From: Matthew Barth <msbarth@linux.ibm.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
Mohaimen Alsamarai <Mohaimen.Alsamarai@fii-na.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"vveerach@google.com" <vveerach@google.com>,
Lancelot Kao <lancelot.cy.kao@fii-na.com>
Subject: Re: group for foxconn CI / fii oem repo
Date: Tue, 16 Mar 2021 09:03:44 -0500 [thread overview]
Message-ID: <9b74a31c-f2e2-c959-6661-e9d3400435b1@linux.ibm.com> (raw)
In-Reply-To: <20210316125616.qnu4bxjzh5ub2fzs@thinkpad.fuzziesquirrel.com>
On 3/16/21 7:56 AM, Brad Bishop wrote:
> On Mon, Mar 15, 2021 at 04:51:50PM -0400, Brad Bishop wrote:
>> On Fri, Mar 12, 2021 at 07:25:42PM +0000, Mohaimen Alsamarai wrote:
>>> Hi Brad,
>>> How can we create Ci group on gerrit and add people to it
>>
>> Created fii/ci-authorized and fii/ci-authorized-owners. Please add
>> people to fii/ci-authorized to automatically approve patch authors for
>> CI.
>
> Yesterday I learned there is an additional step to get automatic CI validation working. There is a script here that needs updating with your fii/ci-authorized group:
>
> https://github.com/openbmc/openbmc-build-scripts/blob/master/jenkins/userid-validation#L42
>
> Can you please add a line similar to all the others but with fii/ci-authorized and then submit that for review to openbmc-build-scripts on our Gerrit instance?
To save yourself some rebasing, I'd suggest pulling down the following change and adding `fii/ci-authorized` to that as the 'userid-validation' script re-work is in flight.
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/41301
>
> thanks - brad
next prev parent reply other threads:[~2021-03-16 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR08MB58838020F8543D03C6235064B2929@DM6PR08MB5883.namprd08.prod.outlook.com>
2021-03-12 19:25 ` group for foxconn CI / fii oem repo Mohaimen Alsamarai
2021-03-15 20:51 ` Brad Bishop
2021-03-16 12:56 ` Brad Bishop
2021-03-16 14:03 ` Matthew Barth [this message]
2021-03-27 14:06 ` Patrick Williams
2021-03-29 18:38 ` Mohaimen Alsamarai
2021-03-29 18:40 ` Lancelot Kao
2021-03-31 20:28 ` krtaylor
2021-04-04 3:43 ` Lancelot Kao
2021-04-19 16:07 ` krtaylor
2021-04-08 15:30 ` Brad Bishop
2021-03-12 19:29 XP Chen
2021-03-12 19:32 ` Lancelot Kao
[not found] <SN6PR08MB50879F47244702D7920CC0AB9C8C9@SN6PR08MB5087.namprd08.prod.outlook.com>
2022-07-25 16:22 ` Brad Bishop
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=9b74a31c-f2e2-c959-6661-e9d3400435b1@linux.ibm.com \
--to=msbarth@linux.ibm.com \
--cc=Mohaimen.Alsamarai@fii-na.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=lancelot.cy.kao@fii-na.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vveerach@google.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).