Pipeline status badge shows policy bot pipelines instead of developer-triggered pipelines
Summary
On the main repository page, there is a small “check mark” icon that represents the commit status. When clicking it, GitLab opens the latest pipeline for that commit. The problem is that in this view, GitLab sometimes shows a pipeline from security scans or background policies, instead of the actual deploy pipeline. As a result, the commit status shows “passed” even though the real deploy pipeline failed.
This creates confusion for users who trust that commit status as a quick indicator of the project health.
Steps to reproduce
I haven't been able to reproduce this, but the customer captured a HAR, a short video recording, along with a brief description of their tests
Notes from their tests;
"at first, in the main window, when we click the commit status it redirects tp the pipeline 28919455, which was triggered by the Gitlab Security Policy Bot, and in the video it can be seen there are 5 pipelines more related to security. But, what we are expecting is that the pipeline 27669742, triggered by Jason Fernandez, is the the one shown on commit status on the main window"
Example Project
What is the current bug behavior?
Root Cause
The badge status logic does not differentiate between pipeline sources. Policy bot pipelines are treated the same as user-triggered deployment pipelines when determining which pipeline to display.
The pipeline doesn't always link to an actual deploy pipeline.
What is the expected correct behavior?
The commit status badge should:
- Link to user-triggered deployment pipelines (not policy bot pipelines)
- Exclude informational pipeline sources (
security_orchestration_policy,pipeline_execution_policy_schedule) from badge display logic - Preserve visibility of policy bot pipeline results elsewhere in the UI (pipeline list, MR widgets, etc.)
The commit "checkmark" should lead to the deploy pipeline for the latest commit
Relevant logs and/or screenshots
See private comment.
Output of checks
Results of GitLab environment info
The customer here is on 18.3.2
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: \\\\\\\`sudo gitlab-rake gitlab:env:info\\\\\\\`) (For installations from source run and paste the output of: \\\\\\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\\\\\`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:check SANITIZE=true\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\\\`) (we will only investigate if the tests are passing)
Possible fixes
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.