Re: Don't run Salsa CI in vain - a disabled CI is better than a persistently failing one
Marco d'Itri <[email protected]>
| Newsgroups | gmane.linux.debian.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On Jun 27, Otto Kekäläinen <[email protected]> wrote: >I'd like to kindly ask maintainers to temporarily disable Salsa CI on >their repositories *if* the pipeline is persistently failing and there >are no immediate plans to fix it. Sometimes the Salsa CI fails because some jobs are stupid, but the results of other jobs are still important. The uscan job is especially bad in this regard, e.g.: * https://salsa.debian.org/salsa-ci-team/pipeline/-/work_items/568 * https://salsa.debian.org/salsa-ci-team/pipeline/-/work_items/569 * any upload of git snapshots that do not follow uscan's author favourite version numbering scheme I guess that at some point I will just disable the uscan job everywhere, since it is clearly doing more harm than good for my own packages. -- ciao, Marco
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCakBkzwAKCRDLPsM64d7X gRiWAP9Y9FkACKscmJgwtX87XHSmk+5kIwSA+0gbp+4z3vs7dwEA294Uchf86QA4 bD9OPCMCDcfxWgZWu+ntRQ0BvBoHxg4= =a06Z -----END PGP SIGNATURE-----