From: "Sean" <sean.brogan@microsoft.com>
To: Rebecca Cran <rebecca@bluestop.org>,devel@edk2.groups.io
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Date: Tue, 14 May 2019 16:23:18 -0700 [thread overview]
Message-ID: <24730.1557876198223366119@groups.io> (raw)
In-Reply-To: <f826b823-3a56-af84-832d-3cc6a2d5f843@bluestop.org>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 418 bytes --]
next prev parent reply other threads:[~2019-05-14 23:23 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 [this message]
2019-05-14 23:34 ` rebecca
2019-05-23 2:39 ` Michael D Kinney
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=24730.1557876198223366119@groups.io \
--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