From: rebecca@bsdio.com
To: rfc@edk2.groups.io, michael.d.kinney@intel.com,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-rfc] [RFC] EDK II Continuous Integration Phase 1
Date: Sat, 31 Aug 2019 14:31:10 -0600 [thread overview]
Message-ID: <3f622621-960e-b187-7cf3-6c8795692f14@bsdio.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9DA6404@ORSMSX113.amr.corp.intel.com>
On 2019-08-29 14:22, Michael D Kinney wrote:
> This is based on work from a number of EDK II community
> members that have provide valuable input and evaluations.
>
> * Rebecca Cran <rebecca@bsdio.com> Jenkins evaluation
> * Laszlo Ersek <lersek@redhat.com> GitLab evaluation
> * Philippe Mathieu-Daudé <philmd@redhat.com> GitLab evaluation
> * Sean Brogan <sean.brogan@microsoft.com> Azure Pipelines and HBFA
> * Bret Barkelew <Bret.Barkelew@microsoft.com> Azure Pipelines and HBFA
> * Jiewen Yao <jiewen.yao@intel.com> HBFA
>
> The following link is a link to an EDK II WIKI page that
> contains a summary of the work to date. Please provide
> feedback in the EDK II mailing lists. The WIKI pages will
> be updated with input from the entire EDK II community.
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Continuous-Integration
Sorry, I was thinking the evaluation I was doing was having the entire
CI run in Jenkins, not only the boot testing. I don't have the array of
hardware you'd want for boot testing, just mostly large x86 systems.
So I think I'll drop out of the evaluation.
--
Rebecca Cran
next prev parent reply other threads:[~2019-08-31 20:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:22 [RFC] EDK II Continuous Integration Phase 1 Michael D Kinney
2019-08-29 20:39 ` [edk2-devel] " Michael Zimmermann
2019-08-29 21:08 ` Michael D Kinney
2019-08-30 2:21 ` Sean
2019-08-30 13:11 ` [edk2-devel] " Laszlo Ersek
2019-09-13 21:00 ` Sean
2019-09-16 11:06 ` Laszlo Ersek
2019-09-19 21:45 ` Michael D Kinney
2019-09-19 21:55 ` Michael D Kinney
2019-09-20 21:29 ` Sean
2019-09-23 17:44 ` Michael D Kinney
2019-09-24 14:05 ` Liming Gao
2019-08-30 8:43 ` Liming Gao
2019-08-30 12:58 ` [edk2-devel] " Laszlo Ersek
2019-09-03 3:39 ` [edk2-rfc] " Ni, Ray
2019-09-03 13:19 ` Laszlo Ersek
2019-09-03 16:41 ` Ni, Ray
2019-09-03 16:55 ` Laszlo Ersek
2019-09-03 17:09 ` Sean
2019-09-03 17:45 ` Laszlo Ersek
2019-09-19 21:13 ` Michael D Kinney
2019-09-04 23:56 ` rebecca
2019-09-19 17:53 ` Michael D Kinney
2019-08-31 20:31 ` rebecca [this message]
2019-09-17 3:46 ` [edk2-devel] " rebecca
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-list 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=3f622621-960e-b187-7cf3-6c8795692f14@bsdio.com \
--to=devel@edk2.groups.io \
/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