From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Cc: cardoe@cardoe.com, michal.orzel@amd.com,
Stefano Stabellini <stefano.stabellini@amd.com>
Subject: Re: [PATCH v2 2/2] automation: introduce a dom0less test run on Xilinx hardware
Date: Mon, 6 Mar 2023 10:25:21 +0000 [thread overview]
Message-ID: <290dec66-c5a5-0609-f95f-7e3bcfd3fc94@citrix.com> (raw)
In-Reply-To: <20230303235719.1181690-2-sstabellini@kernel.org>
On 03/03/2023 11:57 pm, Stefano Stabellini wrote:
> + only:
> + variables:
> + - $XILINX_JOBS == "true" && $CI_COMMIT_REF_PROTECTED == "true"
We don't want to protect every branch of a tree that only a select
number of people can push to, nor (for this, or others configured with
the runner), want to impose branching conventions on them.
In all anticipated cases, those able to push would also be able to
reconfigure the protected-ness of branches, so this doesn't gain us any
security I don't think, but it certainly puts more hoops in the way to
be jumped through.
~Andrew
next prev parent reply other threads:[~2023-03-06 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 23:57 [PATCH v2 0/2] automation: introduce a Xilinx hardware test Stefano Stabellini
2023-03-03 23:57 ` [PATCH v2 1/2] automation: add Ubuntu container for Xilinx hardware tests Stefano Stabellini
2023-03-06 8:39 ` Michal Orzel
2023-03-03 23:57 ` [PATCH v2 2/2] automation: introduce a dom0less test run on Xilinx hardware Stefano Stabellini
2023-03-06 9:21 ` Michal Orzel
2023-03-06 23:15 ` Stefano Stabellini
2023-03-06 10:25 ` Andrew Cooper [this message]
2023-03-06 23:02 ` Stefano Stabellini
2023-03-07 15:21 ` Marek Marczykowski-Górecki
2023-03-07 20:21 ` Stefano Stabellini
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=290dec66-c5a5-0609-f95f-7e3bcfd3fc94@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@amd.com \
--cc=xen-devel@lists.xenproject.org \
/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.