On 8/29/19 2:22 PM, Michael D Kinney wrote:

The following link is a link to an EDK II WIKI page that
contains a summary of the work to date. Please provide
feedback in the EDK II mailing lists. The WIKI pages will
be updated with input from the entire EDK II community.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Continuous-Integration

In that wiki page, it says:

"To work with this branch and run tests immediately, all you need to do is:

|pip install --upgrade -r requirements.txt stuart_setup -c .\CISettings.py stuart_update -c .\CISettings.py stuart_ci_build -c .\CISettings.py --Tool_Chain VS2017" |


I tried doing that in my KUbuntu system, but it was wanting to run NuGet. Once I installed the needed libmono packages via apt, it was wanting to install mu-nasm and then mu-Basetools. I thought it would be pushing changes to Azure to test, not trying to build it locally?


--

Rebecca Cran

Rebecca,

That process is to run the CI process locally.

If you want to run on the Azure servers the idea is you push to a branch that has a CI policy or create a PR to a branch that has this build as a "gate".

So for example if you
1. fork https://github.com/spbrogan/edk2-staging
2. Checkout the edk2-stuart-ci-latest branch from your fork.
3. Make a change and commit it.
4. Push to your fork.
5. Go to your fork on the github website or the PR page of my fork you can create a Pull Request from your branch to mine.
6. Create it. Once you do that it will spawn builds on the server. If I had branch policies that required those builds to pass the PR could not be completed/merged without passing.

Does that help.

Thanks
Sean

On 2019-09-17 15:08, Sean via Groups.Io wrote:

That process is to run the CI process locally.

If you want to run on the Azure servers the idea is you push to a branch that has a CI policy or create a PR to a branch that has this build as a "gate".

So for example if you
1. fork https://github.com/spbrogan/edk2-staging
2. Checkout the edk2-stuart-ci-latest branch from your fork.
3. Make a change and commit it.
4. Push to your fork.
5. Go to your fork on the github website or the PR page of my fork you can create a Pull Request from your branch to mine.
6. Create it. Once you do that it will spawn builds on the server. If I had branch policies that required those builds to pass the PR could not be completed/merged without passing.

Does that help.

Thanks, that does help.


--
Rebecca Cran