public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@bluestop.org" <rebecca@bluestop.org>,
	Sean <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Date: Thu, 23 May 2019 02:39:18 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9D1BC79@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <3008d0b3-2e37-e8f9-5e15-5133f7948579@bluestop.org>

Hi Sean,

Does the PIP module here support both local platform builds and 
CI builds?

I am looking at the name of the repo and trying to align with
the edk2-tools-library repo name so it is obvious the two repos
are related.  Maybe focus on the CI part for the name and we 
reuse the CI features to simplify local builds.

	edk2-tools-ci

Finalizing the name is the only open I am aware of.

Thanks,

Mike

> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io]
> On Behalf Of rebecca@bluestop.org
> Sent: Tuesday, May 14, 2019 4:34 PM
> To: Sean <sean.brogan@microsoft.com>;
> devel@edk2.groups.io
> Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
> 
> On 2019-05-14 17:23, sean.brogan via groups.io wrote:
> > Take a look at the proposed content and how it is
> used.  We even have
> > examples of calling from DevOps and i don't think
> Jenkins would be any
> > different.  I don't think we are trying to duplicate CI
> > functionality.  We are providing the "last mile" so
> that those CI
> > engines can run EDK specific tests and tools.  Standard
> CI engines
> > have no concept of packages, DSC, FDF, INFs, firmware,
> etc.
> 
> 
> Okay, that's great. Of course we do also have lots of
> code running on
> the CI server at work, not the client, that does things
> like packaging
> etc., and this proposal will include server-side code
> too.
> 
> Also, I don't think there is anything that'll be as
> nicely integrated as
> this, so I'm happy with it.
> 
> 
> --
> Rebecca Cran
> 
> 
> 


  reply	other threads:[~2019-05-23  2:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  2:55 RFC for Edk2-ToolEnv Sean
2019-05-14  4:01 ` [edk2-devel] " rebecca
2019-05-14  7:37   ` Sean
2019-05-14 22:24     ` rebecca
2019-05-14 23:23       ` Sean
2019-05-14 23:34         ` rebecca
2019-05-23  2:39           ` Michael D Kinney [this message]
2019-05-23  6:46             ` Sean
2019-05-23 17:14               ` Michael D Kinney
2019-06-11 18:55                 ` Purma, Kondal R
2019-06-12  6:02                   ` Sean
2019-06-28 22:13                     ` Sean
2019-06-28 22:22                       ` Michael D Kinney

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=E92EE9817A31E24EB0585FDF735412F5B9D1BC79@ORSMSX113.amr.corp.intel.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