Sean Whitton writes ("Bug#1111331: git-debpush: check if CI passed before
tagging"):
> For two complex packages I upload, sbcl and Emacs, the CI pipelines on
> salsa were set up by other people and always fail. I've never looked at
> them, leaving it to them. So such a default would very much get in my
> way. So ideally we can come up with something more subtle.
I'm tempted to suggest that if you have a CI pipeline that always
fails you ought to get rid of it :-).
But more practically, would it be terrible if this situation required
configuration somewhere? Places this could go include
(a) git config in your local tree
(b) something in the git tree object
(c) command line option
I think (b) is probably an OK choice.
At some point we're going to want to do maintainer-workflow-agnostic
NMUs. This is yet another case where the non-maintainer-workflow
upload needs different handling. I guess a non-maintainer-workflow
NMU is going to have a different remote since it mustn't push the dgit
view tag with the DEP0-14 name to salsa. So that's a way to tell them
apart.
So how about a t2u config file in debian/, somewhere? For your
packages with broken CI it oculd say "disregard CI for
salsa.debian.org" or "disregard CI for all gitlab forges".
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
