From: Cleber Rosa <crosa@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Willian Rampazzo" <wrampazz@redhat.com>
Subject: Re: gitlab-ci: Only build /staging branch?
Date: Wed, 24 Mar 2021 19:11:56 -0400 [thread overview]
Message-ID: <20210324231156.GG3592254@amachine.somewhere> (raw)
In-Reply-To: <2da69b21-ce5e-cae2-68ef-d6e042563a3a@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Wed, Mar 24, 2021 at 07:01:12PM +0100, Philippe Mathieu-Daudé wrote:
> Hi,
>
> Peter's current workflow is push to /staging and if his
> testing succeeds, he pushes the same commit as /master.
>
> IMO there is no point in building /master branch, as it
> has already been built earlier as /staging.
>
Hi,
I agree, I currently see no point in running the entire pipeline
again.
But we need to watch out for the job conditional rules. For instance,
both of these pipelines are about the exact same commit:
https://gitlab.com/qemu-project/qemu/-/pipelines/275925246
https://gitlab.com/qemu-project/qemu/-/pipelines/275925289
But one has 113, while the other has 119 jobs. Also, we may want
to check if tags also trigger new (unnecessary) pipelines.
> Regards,
>
> Phil.
>
Best,
- Cleber
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-03-24 23:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 18:01 gitlab-ci: Only build /staging branch? Philippe Mathieu-Daudé
2021-03-24 18:33 ` Philippe Mathieu-Daudé
2021-03-24 21:58 ` Philippe Mathieu-Daudé
2021-03-25 5:43 ` Thomas Huth
2021-03-25 9:29 ` Philippe Mathieu-Daudé
2021-03-25 9:50 ` Philippe Mathieu-Daudé
2021-03-25 10:34 ` Peter Maydell
2021-03-25 11:05 ` Paolo Bonzini
2021-03-25 11:06 ` Peter Maydell
2021-03-25 11:14 ` Daniel P. Berrangé
2021-03-24 23:11 ` Cleber Rosa [this message]
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=20210324231156.GG3592254@amachine.somewhere \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).