* Chris Hofstaedtler <[email protected]> [260724 15:34]:
* Otto Kekäläinen <[email protected]> [260718 07:18]:
Hi,
Alert fatigue is a well known phenomenon. The purpose of a CI system
is to be 99% green. In the 1% of cases where it fails, it should cause
development to stop so developers can research why, and fix a
regression before it goes into production or before new feature
development continues.
Maybe you should investigate
https://salsa.debian.org/salsa-ci-team/pipeline/-/commits/master?ref_type=heads
which seems to be have a lot more than 1% failed pipelines.... :)
The git HEAD is and was green when you wrote this. As the this git
repo has no releases, only the HEAD passing all CI matters.
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?
I notice the pipeline for
https://salsa.debian.org/salsa-ci-team/pipeline/-/commits/master?ref_type=HEADS
is also red, incl. on Otto's commit
964d824a0bcf63c2a12a562aa57e9825534f3b16 from a month ago.
¯\(ツ)/¯
Chris
