public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, sean.brogan@microsoft.com,
	Shenglei <shenglei.zhang@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 0/6] Edk2 Platform and Core CI for ArmVirtPkg, EmulatorPkg, and OvmfPkg
Date: Wed, 15 Apr 2020 14:22:36 -0600	[thread overview]
Message-ID: <33e62be3-5cb2-67c7-1d8b-adf9d83bdeb4@bsdio.com> (raw)
In-Reply-To: <31845.1586967303895736411@groups.io>

On 4/15/2020 10:15 AM, Sean via groups.io wrote:
> 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.


In my opinion there's something wrong with the CI framework if it can 
only easily be run in the Azure DevOps environment. And the use of Azure 
shouldn't become a requirement, in my opinion.


-- 
Rebecca Cran



  reply	other threads:[~2020-04-15 20:22 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 [this message]
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=33e62be3-5cb2-67c7-1d8b-adf9d83bdeb4@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