pipelines: default: - step: script: - echo Hello custom: manual-pipeline: - step: script: - echo Hello
Normally, when you run a branch pipeline (via a push) and a manual pipeline (on a commit), they will show as two different builds on the Build Status dialog for a specified commit.
However, it is possible to have the manual pipeline override the build status of the branch pipeline. This is caused by triggering the manual pipeline on the Branches Page instead of on an individual commit.
Steps to reproduce:
- Use the YAML specified above.
- Trigger a push pipeline on a specific branch (we'll call this foo-branch).
- This will have also created a new commit on the branch (called abc123)
- Go to the Branches Page, and select the "..." for the 'foo-branch' branch. Select "Run pipeline for a branch" and then "manual-pipeline".
- Go to the commit, and see that the build status still only shows one build, which now links to the newly triggered "manual-pipeline".
Both the automatically push triggered branch pipeline and the manually triggered pipeline should show on this commit.
Similar behaviour can also be seen on the Build Status of a Pull Request.