action #73360
closedmerging MRs in openqa/salt-states-openqa does not trigger pipeline in master
0%
Description
Observation¶
See https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/379
after merge this did not trigger a pipeline run. Maybe we lost something in https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/347 ? But it does not look like it could explain it.
Workaround¶
Trigger CI pipeline manually in https://gitlab.suse.de/openqa/salt-states-openqa/-/pipelines/new or fetch git repo update on osd in /srv/salt manually and apply.
Updated by okurz over 3 years ago
https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/381 is a MR from mkittler which when merged by me did the same. So at least it is not just because of MRs from me :)
Updated by okurz over 3 years ago
- Status changed from New to Blocked
- Assignee set to okurz
Since some days, probably since a change within the gitlab.nue.suse.com infrastructure merging merge requests on gitlab.nue.suse.com does not trigger pipelines anymore. I reported this initially here assuming it was my problem but José Gómez @josegomezr and Farah Schueller @farahschueller have reported the same issue, see https://chat.suse.de/channel/suse-it-ama?msg=n4cMms9qwcH78TfWp and following. I have now reported
https://infra.nue.suse.com/SelfService/Display.html?id=178470
Updated by okurz over 3 years ago
- Status changed from Blocked to Resolved
the ticket has received no update yet but a new version of gitlab was installed. And rklein mentioned in https://chat.suse.de/channel/suse-it-ama?msg=zEqnXdASx2BxuJ97Z that the issue should be gone. I updated https://infra.nue.suse.com/SelfService/Display.html?id=178470 . I just merged https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/386 and it triggered a gitlab CI pipeline as expected.