From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Willian Rampazzo <wrampazz@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: gitlab-ci: Only build /staging branch?
Date: Wed, 24 Mar 2021 22:58:43 +0100 [thread overview]
Message-ID: <74859ed9-6f93-0b8a-a669-6aef1e164e41@amsat.org> (raw)
In-Reply-To: <8ec8b3b7-12b4-b676-630c-972e7038ec7f@amsat.org>
On 3/24/21 7:33 PM, Philippe Mathieu-Daudé wrote:
> On 3/24/21 7:01 PM, 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.
Similarly with tags. Although we don't tag often.
Suggestion:
- staging: always build
- tags: on-demand build (manual)
- master: no build
Thinking about reproducible artifacts, we could have a tag job
to produce the archive with submodules, but someone still have
to sign it.
Thoughts?
next prev parent reply other threads:[~2021-03-24 22:01 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é [this message]
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
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=74859ed9-6f93-0b8a-a669-6aef1e164e41@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--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).