From: "Rebecca Cran" <rebecca@bsdio.com>
To: Sean <sean.brogan@microsoft.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v1 0/6] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg
Date: Wed, 15 Apr 2020 15:08:27 -0600 [thread overview]
Message-ID: <ae3376f0-e35f-8413-cd11-50c2e1c883fd@bsdio.com> (raw)
In-Reply-To: <5211.1586983478083118979@groups.io>
On 4/15/2020 2:44 PM, sean.brogan via [] wrote:
>
> Each CI framework has different syntax, capabilities, and
> requirements. The PyTools environment attempts to generalize the
> edk2/uefi aspects of the setup, build, and test but regardless there
> are things that should be done as "steps" in the CI framework being
> targeted. This is why there is a split between PlatformBuild.py and
> the azurepipelines files. PlatformBuild.py and the ReadMe.md files
> all have details about how to run locally as well so those aspects can
> be tested independently from the CI framework.
I had difficulty running the PyTools locally, so I thought there was an
idea to only support running it on Azure. Thanks for the clarification.
--
Rebecca Cran
next prev parent reply other threads:[~2020-04-15 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 18:13 [PATCH v1 0/6] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg Michael Kubacki
2020-04-14 8:31 ` [edk2-devel] " Zhang, Shenglei
2020-04-15 6:51 ` Sean
2020-04-15 7:13 ` Zhang, Shenglei
2020-04-15 16:15 ` Sean
2020-04-15 20:22 ` Rebecca Cran
2020-04-15 20:44 ` Sean
2020-04-15 21:08 ` Rebecca Cran [this message]
2020-04-15 21:14 ` Sean
2020-04-17 7:39 ` Zhang, Shenglei
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=ae3376f0-e35f-8413-cd11-50c2e1c883fd@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