It's a "being gaslit by the CI server" kind of day
=> More informations about this toot | More toots from directhex@tech.lgbt
I think GitLab wanted vengeance against me for not having reason to complain for nearly 2 weeks. I've got 2 weeks of pent up CI misbehaviour in one inexplicable bug to try and figure out.
=> More informations about this toot | More toots from directhex@tech.lgbt
The issue describing GL's failure on this was opened FIVE YEARS AGO.
"SLO Missed" indeed.
=> More informations about this toot | More toots from directhex@tech.lgbt
when: manual
WHY DOES THIS DISABLE ALLLLLL OTHER UNRELATED JOBS IN A PIPELINE
=> More informations about this toot | More toots from directhex@tech.lgbt
@directhex I can feel the frustration from this side of the pond
=> More informations about this toot | More toots from ludovic_dev@mastodon.social
@directhex It's not because of implicit dependencies between pipeline stages, is it?
=> More informations about this toot | More toots from bwh@tech.lgbt
@bwh as best i can determine, it’s a broken interaction between “this is a MR build” and “this is a branch build” of the same commit. What’s particularly fishy is the MR build fully ignores a strict needs: on one of the jobs it’s decided to suppress, and allows the new manual job to just ignore it silently
=> More informations about this toot | More toots from directhex@tech.lgbt This content has been proxied by September (3851b).Proxy Information
text/gemini