From: Patrick Williams <patrick@stwcx.xyz>
To: Andrew Geissler <geissonator@gmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"bradleyb@fuzziesquirrel.com" <bradleyb@fuzziesquirrel.com>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
Patrick Williams <patrickw3@fb.com>
Subject: Re: CI build for yosemitev2
Date: Fri, 23 Apr 2021 08:20:50 -0500 [thread overview]
Message-ID: <YILJsgzS9otvmnJL@heinlein> (raw)
In-Reply-To: <20210115132613.GA47865@patrickw3-mbp.dhcp.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Fri, Jan 15, 2021 at 07:26:13AM -0600, Patrick Williams wrote:
> On Sun, Jan 03, 2021 at 07:27:06PM -0600, Andrew Geissler wrote:
> > > On Dec 21, 2020, at 9:32 AM, Velumani T-ERS,HCLTech <velumanit@hcl.com> wrote:
> > > Could you please help us to add the Yosemitev2 machine in the CI build verification.
>
> > 2) Donate a jenkins compute node to openbmc CI
>
> Facebook will allocate a few compute nodes to the Jenkins pool. Andrew,
> I'll work with you to get them online and integrated with Jenkins. Once
> that is done, we can enable Yv2?
I wanted to follow up and let everyone know that this work effort is
done and Yv2 is now enabled in CI. Facebook is currently contributing 4
pretty fast machines to the Jenkins pool.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-23 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 15:32 CI build for yosemitev2 Velumani T-ERS,HCLTech
2021-01-04 1:27 ` Andrew Geissler
2021-01-12 5:09 ` Velumani T-ERS,HCLTech
2021-01-12 5:33 ` [External] " Lei Yu
2021-01-15 13:26 ` Patrick Williams
2021-01-15 14:12 ` Andrew Geissler
2021-04-23 13:20 ` Patrick Williams [this message]
2021-04-23 13:52 ` Velumani T-ERS,HCLTech
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=YILJsgzS9otvmnJL@heinlein \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrickw3@fb.com \
--cc=velumanit@hcl.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 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.