public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Sean <sean.brogan@microsoft.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] [RFC] EDK II Continuous Integration Phase 1
Date: Mon, 16 Sep 2019 13:06:43 +0200	[thread overview]
Message-ID: <592f587b-86cb-cb48-4816-8781b20b0b5d@redhat.com> (raw)
In-Reply-To: <10937.1568408459627289047@groups.io>

Hi Sean,

On 09/13/19 23:00, sean.brogan via [] wrote:
> These tests require using the "edk2-pytool" stuff but are easy to integrate with the github PR or CI flow.  Example of it running the code compliance tests is here: https://dev.azure.com/tianocore/edk2-ci-play/_build?definitionId=13&_a=summary A test run takes about 3 minutes.
> 
> The past week or so we also have been working on a more complete test run which adds to the above test suite three more tests.  Compile each package for Debug, Release, and Host Based Unit tests.  Obviously this adds more time and takes more resources but at the moment we have it down to 13 minutes. You can see it here: https://dev.azure.com/tianocore/edk2-ci-play/_build?definitionId=12&_a=summary
> 
> To enable this framework you need the following.
> 
> 1. pip install a couple of edk2-pytool packages (see requirements.txt file)
> 2. Add the pytool based plugins to the edk2 code tree  See here: https://github.com/spbrogan/edk2-staging/tree/edk2-stuart-ci-latest/BaseTools/Plugin/Ci
> 3. Add a CiSettings.py file that satisfies the setup, update, and ci_build  See here: https://github.com/spbrogan/edk2-staging/blob/edk2-stuart-ci-latest/CISettings.py
> 4. Add a *.ci.yaml file to each package to configure test settings, ignore files, and other configuration for testing the package.  Example here: https://github.com/spbrogan/edk2-staging/blob/edk2-stuart-ci-latest/MdeModulePkg/MdeModulePkg.ci.yaml
> 5.  For Azure pipeline support (cloud based CI) you will need to add Azure pipeline.yaml flles.
> 
> This can all be seen in the branch here. https://github.com/spbrogan/edk2-staging/tree/edk2-stuart-ci-latest
> Be aware that in that same branch we are enabling "Host based unit tests" which also requires more code changes so if diffing with clean edk2 you can ignore those (although that is all part of another RFC for unit test so any feedback on that would be great too).
> 
> Feedback would be appreciated.  I am hoping this RFC can move forward in the next few weeks.

I'm really sorry, I don't have any cycles left for this topic at the
moment. I hope Mike and others can proceed with you.

(I prefer to share whenever I'm out of time for a topic; I find that a
lot better than unjustifiedly blocking others from doing their work.)

Thanks & sorry again
Laszlo

  reply	other threads:[~2019-09-16 11:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 20:22 [RFC] EDK II Continuous Integration Phase 1 Michael D Kinney
2019-08-29 20:39 ` [edk2-devel] " Michael Zimmermann
2019-08-29 21:08   ` Michael D Kinney
2019-08-30  2:21 ` Sean
2019-08-30 13:11   ` [edk2-devel] " Laszlo Ersek
2019-09-13 21:00     ` Sean
2019-09-16 11:06       ` Laszlo Ersek [this message]
2019-09-19 21:45   ` Michael D Kinney
2019-09-19 21:55   ` Michael D Kinney
2019-09-20 21:29     ` Sean
2019-09-23 17:44       ` Michael D Kinney
2019-09-24 14:05         ` Liming Gao
2019-08-30  8:43 ` Liming Gao
2019-08-30 12:58   ` [edk2-devel] " Laszlo Ersek
2019-09-03  3:39     ` [edk2-rfc] " Ni, Ray
2019-09-03 13:19       ` Laszlo Ersek
2019-09-03 16:41         ` Ni, Ray
2019-09-03 16:55           ` Laszlo Ersek
2019-09-03 17:09             ` Sean
2019-09-03 17:45               ` Laszlo Ersek
2019-09-19 21:13                 ` Michael D Kinney
2019-09-04 23:56           ` rebecca
2019-09-19 17:53   ` Michael D Kinney
2019-08-31 20:31 ` [edk2-rfc] " rebecca
2019-09-17  3:46 ` [edk2-devel] " rebecca

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=592f587b-86cb-cb48-4816-8781b20b0b5d@redhat.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