action #77101
closed
action #77089: [osd][retrospective] multiple unattended alerts, unattended gitlab CI pipeline fails, all osd aarch64 workers offline
fix selection of gitlab CI runners
Added by okurz about 4 years ago.
Updated about 4 years ago.
Description
Observations¶
All gitlab.suse.de CI jobs using shared runners fail to run on any worker. Seems like we need an explicit defaults:\n tags: [docker] now.
<okurz> I don't mind the tag but it seems an explicit tag is now required where previously it was not. IIUC an empty .gitlab-ci.yml should still be picked by a shared runner. Did you try this yourself or do you have other tests for your infrastructure?
<rklein> let me test it and if that's the case, I will try to find out how to change it back, now I see what you are talking... you are probably correct....
<rklein> I'm sorry, you are completely correct... there is a checkbox saying `Run untagged jobs` and I forgot to check it. I'm sorry, fixing it
<rklein> all fixed
so we should not need the above.
- Status changed from In Progress to Resolved
Closed my MRs again and reverted the changes I had already applied.
- Related to action #76774: auto-review/openqa-label-known-issues does not conclude within GitLab CI added
Also available in: Atom
PDF