openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gilbert Chen <Gilbert.Chen@arm.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: request to add Gilbert Chen to CLA repository ACL
Date: Wed, 16 Feb 2022 13:48:55 +0000	[thread overview]
Message-ID: <PAXPR08MB6560715A7152F90C9274667B86359@PAXPR08MB6560.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PAXPR08MB6560E663519DBD5399A077CB862F9@PAXPR08MB6560.eurprd08.prod.outlook.com>

Hi Brad,

The change of openbmc-build-scripts has been merged. My gerrit account is also in arm/ci-authorized group.
But the gerrit patch I submited still cannot let OpenBMC CI work for me. When I push new commit.
The change log of gerrit still shows "User not approved, see admin CI"
https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/51184

Sorry for trouble you again. Do you know if anything I missed?

Thanks,
Gilbert

-----Original Message-----
From: Gilbert Chen
Sent: Thursday, February 10, 2022 9:15 PM
To: 'Brad Bishop' <bradleyb@fuzziesquirrel.com>; openbmc@lists.ozlabs.org
Subject: RE: request to add Gilbert Chen to CLA repository ACL

Hi Brad,

Thanks for your help. I have submitted a change to add arm in /jenkins/userid-validation
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/51125

Gilbert

-----Original Message-----
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
Sent: Thursday, February 10, 2022 7:50 PM
To: Gilbert Chen <Gilbert.Chen@arm.com>; openbmc@lists.ozlabs.org
Subject: Re: request to add Gilbert Chen to CLA repository ACL

On Thu, 2022-02-10 at 12:52 +0000, Gilbert Chen wrote:
> Hi,
>
> Can you help add me to appropriate CLA repository ACL since I want to
> submit code changes to gerrit but the gerrit shows "OpenBMC CI - User
> not approved, see admin, no CI".
>
> I have been added in ARM CCLA.
> https://drive.google.com/file/d/1i0SkfLvR9_loRTZ0zZmC6L_sDOZyQjZB/view
>
> Thanks,
> Gilbert

Hi Gilbert

I created arm/ci-authorized and arm/ci-authorized-owners groups on Gerrit.  I put Samer in arm/ci-authorized-owners so he should be able to add additional people to arm/ci-authorized in the future.

Before CI will use these groups though, you'll have to submit a change similar to this one:

https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/46093
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2022-02-16 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 12:52 request to add Gilbert Chen to CLA repository ACL Gilbert Chen
2022-02-10 19:49 ` Brad Bishop
2022-02-10 21:14   ` Gilbert Chen
2022-02-16 13:48     ` Gilbert Chen [this message]
2022-02-16 17:56       ` Brad Bishop
2022-02-16 21:09         ` Patrick Williams

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=PAXPR08MB6560715A7152F90C9274667B86359@PAXPR08MB6560.eurprd08.prod.outlook.com \
    --to=gilbert.chen@arm.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.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 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).