From: "Sean" <sean.brogan@microsoft.com>
To: Zhang, Shenglei <shenglei.zhang@intel.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 09:15:03 -0700 [thread overview]
Message-ID: <31845.1586967303895736411@groups.io> (raw)
In-Reply-To: <C0706E73DB8C124D9B9C38AA364E5D5E0605EDC9@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
No local server. I use a free devops account. When i was standing up the original Core CI project for tianocore I created a Azure devops project here https://dev.azure.com/tianocore/edk2-ci-play
In this project I can connect to my fork on github and run builds. Anyone else could also setup their own free Azure devops project and connect it to your own github fork of edk2 to test it. This should be a requirement as it took me dozens of runs to get everything working and passing as well as to adjust the syntax to leverage shared files as much as is practical.
Actually after the patchset is accepted and the files committed there will need to be one more commit that changes the links for the build badges (in the readme) to point to the "official" versions. Right now they are pointing at my builds in edk2-ci-play.
thanks
sean
[-- Attachment #2: Type: text/html, Size: 991 bytes --]
next prev parent reply other threads:[~2020-04-15 16:15 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 [this message]
2020-04-15 20:22 ` Rebecca Cran
2020-04-15 20:44 ` Sean
2020-04-15 21:08 ` Rebecca Cran
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=31845.1586967303895736411@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