Hi Sean,
The edk2-pytool-extensions repo has been created.
Thanks,
Mike
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Sean via
Groups.Io
Sent: Friday, June 28, 2019 3:14 PM
To: Sean ; devel@edk2.groups.io
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Wrapping up all
Both of these RFCs listed flake8 because that is what we have today and it
should be relatively easy to get parity. I am super happy to have you
add/propose/provide pr with additional test capability like Pylint. Thats one
of the goals of adding this to tianocore.
You can see what we are
@edk2.groups.io] On Behalf Of Michael D
Kinney
Sent: Thursday, May 23, 2019 10:14 AM
To: devel@edk2.groups.io; sean.bro...@microsoft.com; Kinney, Michael D
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Hi Sean,
Thanks for the clarification that this PIP module has more than just build and
CI
ups.io
> [mailto:devel@edk2.groups.io] On Behalf Of Sean via
> Groups.Io
> Sent: Wednesday, May 22, 2019 11:46 PM
> To: Kinney, Michael D ;
> devel@edk2.groups.io
> Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
>
> Yes the plan would be to support both CI and local
> builds. There
proposed.
Thanks
Sean
-Original Message-
From: Kinney, Michael D
Sent: Wednesday, May 22, 2019 7:39 PM
To: devel@edk2.groups.io; rebe...@bluestop.org; Sean Brogan
Subject: RE: [edk2-devel] RFC for Edk2-ToolEnv
Hi Sean,
Does the PIP module here support both local platform builds
Sean ;
> 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
>
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
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
On 2019-05-14 01:37, Sean via Groups.Io wrote:
>
> If you know of anything I am interested as I don't like building and
> supporting something unnecessary.
>
> This tooling isn't trying to reinvent anything but is really focused
> on providing reusable/sharable functionality that can then be
Rebecca,
If you know of anything I am interested as I don't like building and supporting
something unnecessary.
This tooling isn't trying to reinvent anything but is really focused on
providing reusable/sharable functionality that can then be pieced together by a
platform to produce the
On 2019-05-13 20:55, Sean via Groups.Io wrote:
>
> RFC Edk2-ToolEnv creation
>
>
>
> Create a new tianocore owned repository to host python code to support
> an extensible, pluggable, rich environment. This environment has
> command line interfaces to support building a product, building CI,
>
RFC Edk2-ToolEnv creation
Create a new tianocore owned repository to host python code to support an
extensible, pluggable, rich environment. This environment has command line
interfaces to support building a product, building CI, running tests, and
downloading dependencies. This environment
12 matches
Mail list logo
