Wrong pipeline associated with tag
Summary
- In the tag overview page under
/-/tags
, the pipeline displayed next to a tag is shown as failing (red x), despite the pipeline having ran through successfully when the tag was created. - The reason seems to be that a new pipeline has been associated with the tag, when a new branch was created from the tag and pushed to remote without any changes (this pipeline then failed, because it pointed to a different database, this is expected behavior). I presume the mapping between tag and pipeline is performed based on commit ID?
- This results in an invalid state, since the pipeline shown next to a tag is not the pipeline that was ran when the tag was created
Steps to reproduce
- Create a tag
t
of main, take not of the pipeline ID:p1
and commit ID:#c1
- Using git, branch of main and push the new branch to remote without any commits, which triggers a new pipeline
p2
based of#c1
- Check the the pipeline displayed next to tag
t
on the/-/tags
page. It should bep1
, but insteadp2
is displayed.
What is the current bug behavior?
Pipeline p2
is displayed next to tag t
What is the expected correct behavior?
Pipeline p1
shhould be displayed next to tag t
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com