Page MenuHomePhabricator

[toolforge-cd] remove duplicated run on tag and push to master (just do one if possible)
Closed, ResolvedPublicBUG REPORT

Description

It seems like we are running two gitlab ci/cd pipelines after a patch is merged and this seems to have been going on for sometime now.
For example after patch !51 was merged 1 month ago pipeline 31240 was executed (this is the expected pipeline). But then after the first pipeline executed after merge there is a second pipeline 31242 and this pipeline only ran pre-commit and blubber-test (which was already done in the last ci/cd pipeline).

This is probably a bug but in case it is not, can someone who know about it comment?

Details

TitleReferenceAuthorSource BranchDest Branch
[gitlab-cd] add ci rules to pre-commit and blubber-testrepos/cloud/cicd/gitlab-ci!30raymond-ndibeadd_rules_to_pre_commit_and_blubber_testmain
Customize query in GitLab

Event Timeline

Raymond_Ndibe changed the task status from Open to In Progress.Dec 15 2023, 10:46 PM
Raymond_Ndibe claimed this task.
Raymond_Ndibe updated the task description. (Show Details)

The difference is in the trigger, one was triggered by the push to main, and the other by the tag creation (due to the release creation), we can skip the second adding a filter to the tests.

dcaro triaged this task as Medium priority.Feb 7 2024, 10:12 AM
dcaro renamed this task from [toolforge-cd] find out why we run two gitlab ci/cd pipelines after merge to [toolforge-cd] remove duplicated run on tag and push to master (just do one if possible).Mar 5 2024, 2:35 PM