From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure
Date: Wed, 15 Sep 2021 13:16:32 +0100 [thread overview]
Message-ID: <YUHkIOhcV4Z4Iv1P@redhat.com> (raw)
In-Reply-To: <CAFEAcA9CjgNrGJN2t40PJW6ZO-fP9R0senq4_G_h_8pmjH5n9Q@mail.gmail.com>
On Wed, Sep 15, 2021 at 01:12:23PM +0100, Peter Maydell wrote:
> On Wed, 15 Sept 2021 at 09:29, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > Urgh, my bad, I completely forget this behaviour when reviewing.
> > When we only have
> >
> > when: manual
> >
> > then the job has to be manually started, and it still contributes
> > to pipeline status, so it /must/ triggered manually.
> >
> > If we want it to be manually started and not contribute to the
> > pipeline status we need:
> >
> > rules:
> > ...
> > when: manual
> > allow_failure: true
>
> So there's no way to say "if it is triggered, then it must
> not fail, but if it is not triggered, that's OK" ?
Not that I've found.
> I guess it's not a big deal either way though.
> So the fix is to add back the allow_failure tag to those jobs
> which are manual. I'll send a patch...
Note "allow_failure" is allowed both at the top level of the job
and inside the "rules:". I find it clearer if we put it against
the "rules:" section as shown above.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-09-15 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 10:19 [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure Peter Maydell
2021-09-13 10:28 ` Daniel P. Berrangé
2021-09-13 10:35 ` Peter Maydell
2021-09-13 10:40 ` Daniel P. Berrangé
2021-09-13 15:28 ` Willian Rampazzo
2021-09-14 5:44 ` Thomas Huth
2021-09-14 16:03 ` Peter Maydell
2021-09-14 19:17 ` Peter Maydell
2021-09-14 20:03 ` Willian Rampazzo
2021-09-15 8:29 ` Daniel P. Berrangé
2021-09-15 8:40 ` Philippe Mathieu-Daudé
2021-09-15 12:12 ` Peter Maydell
2021-09-15 12:16 ` Daniel P. Berrangé [this message]
2021-09-15 12:22 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YUHkIOhcV4Z4Iv1P@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wrampazz@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.