* Otto Kekäläinen <[email protected]> [260929 04:22]:
Hi Chris,
...
>>If you or others have CI enabled on projects where you can't fix the
>>repo so CI passes and git HEAD gets green, please scale down testing
>>scope until it passes, or disable the CI.
>
>That's all nice, but when the CI config changes after setting it up
>and then breaks, we can't expect everybody to run around busily and
>disable newly failing or even newly appearing jobs.
https://salsa.debian.org/debian/shadow/-/pipelines/1178928
| Unable to run pipeline
| jobs:extract-source:script config should be a string or a nested array of
strings up to 10 levels deep
I don't know what that means or why it happens. Maybe including yaml
files is just a bad idea? If there was some change src:shadow should
have followed, were there bugs filed about that change that I've
missed?
Last time the CI in shadow passed was in August 2025 [1]. It started
failing in September 2025 [2]. You should have at that point
investigated and updated the gitlab-ci.yml in that project instead of
letting it fail for over a year. Now the CI in that project is running
in vain and not catching any regressions that might have happened in
between. The point of my email was to recommend that if you don't
maintain the CI and try to fix it, you (and all of Salsa) is better
off it you just remove that gitlab-ci.yml file from the project. No CI
is better than a failing CI. Maybe some other day somebody who wants
to contribute to shadow adds back a salsa-ci.yml with a working
configuration. Who knows, perhaps even the vanilla config without any
custom stuff might work for this package (I didn't try).
[..]
Having failing CI for a year like in 'shadow' does not help catch any
regressions, and only wastes resources for others who do want to run
CI and who do look at results and address issues when CI flips from
green to red.
Okay, I will delete the config. The error is not actionable for me.
Chris
