20 September 2018

Posting test results to GitHub/GitLab

Posting test results to GitHub/GitLab

Buddy automatically sends pipeline status to GitHub and GitLab. Setting up a single pipeline with a wildcard * mode will test code in all your branches and give a corresponding status:

GitHub commits list

Using status checks can improve the overall quality of the code. For example, if you use Gitflow, you can configure GitHub to block merging pull requests that have failed the tests: buddy.works/guides/how-protect-code-on-github-with-buddy

Disable Status Sending

However, for specific use cases you may want to disable sending status checks. Let's assume you have a project with a number of pipelines:

  • unit test pipeline run on every push to repo
  • integration test pipeline on the Staginge branch run once a day
  • delivery pipeline for code deployment to Dev/Stage/Production in manual mode

Buddy pipelines

The execution status for each pipeline is automatically sent to GitHub/GitLab. However, there are cases where you don't want that – for example, when all tests are passing but there's a connection error during the deployment. From now on, status sending can be disabled in the pipeline options:

Disabling commit status

Buddy is 100% customer driven. If there’s a feature or integration you miss, let us know in the comments below or directly at support@buddy.works.

Buddy Makes Developers Happier

You use lots of tools to get web & app development done. Buddy creates more time in your day by helping you automate those tools.

Sign up for free with

Six Flags
Public Health England