From: "PierreGondois" <pierre.gondois@arm.com>
To: devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Leif Lindholm <leif@nuviainc.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: [PATCH edk2-platforms v6 0/6] Enable edk2-platforms CI for JunoPkg
Date: Wed, 17 Nov 2021 14:05:22 +0000 [thread overview]
Message-ID: <20211117140528.13600-1-Pierre.Gondois@arm.com> (raw)
From: Pierre Gondois <Pierre.Gondois@arm.com>
v6:
- New patch not have the edk2 repository as an external dependency
instead of a submodule. [Michael]
- Use EDK2_REPO to use a custom edk2 repository instead of downloading
it. [Pierre]
- PatchCheck to install pip-requirements and download edk2. [Pierre]
v5:
- Remove Signed-off from Sami (I replaced it with Co-authored-by)
[Leif]
- Update edk2 submodule to latest master. [Pierre]
v4:
- Checkout edk2 repository in Ubuntu-PatchCheck.yml to
get the PatchCheck.py script. [Pierre]
v3:
- Replace Readme(s)'s by a reference to the initial Readmed(s) in
tianocore repository. [Sean]
- Align CI files with the latest version in the edk2 repository.
[Sean/Michael]
- Add additional step to checkout edk2's latest master in the CI.
[Pierre]
v2:
- Use tianocore repository instead of personal repository
for edk2 submodule [Pierre]
- Bugzilla associated to the topic:
https://bugzilla.tianocore.org/show_bug.cgi?id=3509
It provides the configuration files necessary to run an upstream CI
similar to the one currently used for the main edk2 repository. The
configuration is mostly similar aswell.
Enabling the CI requires administrator rights on the edk2-platforms
repository. This configuration was tested on a private repository,
but will require additional configuration from the administrator.
CI plugins (.pytool/Plugin/) and BaseTools are located in the
Tianocore edk2 repository. To re-use them, add the edk2 repository
as an external dependency.
It is not currently possible to specify a branch name in the "version"
field. Thus, a fixed commit hash (current edk2 master) is written.
It will eventually be replaced by 'master'.
If a platform requires a specific version of edk2, another description
of the edk2 repository in the edk2_ext_dep.yaml can be added. Only the
edk2 repository with the right scope will be installed.
It is possible to use a custom edk2 repository instead. To do so, run
the stuart_[update|build] commands with EDK2_REPO pointing to your
custom edk2 repository.
Compared to edk2's CI, some steps are modified and indicated by
EDK2_PLATFORMS_MODIF_[START|END] statements.
The changes can be seen at:
https://github.com/PierreARM/edk2-platforms/tree/1628_Enable_edk2_platforms_ci_for_JunoPkg_v6
Pierre Gondois (6):
pip-requirements.txt: Add python pip requirements file
CI: Add Tianocore edk2 as an external dependency
.pytool/Plugin: Add CI plugins
.azurepipelines: Add Azure Pipelines YML configuration files
.mergify: Add Mergify YML pull request rules configuration file
Platform/ARM: Juno: Add JunoPkg.ci.yaml for CI support
.azurepipelines/ReadMe.md | 5 +
.azurepipelines/Ubuntu-GCC5.yml | 21 ++
.azurepipelines/Ubuntu-PatchCheck.yml | 55 ++++++
.azurepipelines/Windows-VS2019.yml | 20 ++
.azurepipelines/templates/ReadMe.md | 5 +
.../templates/pr-gate-build-job.yml | 43 ++++
.azurepipelines/templates/pr-gate-steps.yml | 142 +++++++++++++
.../templates/spell-check-prereq-steps.yml | 22 +++
.mergify/config.yml | 50 +++++
.pytool/CISettings.py | 186 ++++++++++++++++++
.pytool/Readme.md | 30 +++
Platform/ARM/JunoPkg/JunoPkg.ci.yaml | 104 ++++++++++
edk2_ext_dep.yaml | 15 ++
pip-requirements.txt | 18 ++
14 files changed, 716 insertions(+)
create mode 100644 .azurepipelines/ReadMe.md
create mode 100644 .azurepipelines/Ubuntu-GCC5.yml
create mode 100644 .azurepipelines/Ubuntu-PatchCheck.yml
create mode 100644 .azurepipelines/Windows-VS2019.yml
create mode 100644 .azurepipelines/templates/ReadMe.md
create mode 100644 .azurepipelines/templates/pr-gate-build-job.yml
create mode 100644 .azurepipelines/templates/pr-gate-steps.yml
create mode 100644 .azurepipelines/templates/spell-check-prereq-steps.yml
create mode 100644 .mergify/config.yml
create mode 100644 .pytool/CISettings.py
create mode 100644 .pytool/Readme.md
create mode 100644 Platform/ARM/JunoPkg/JunoPkg.ci.yaml
create mode 100644 edk2_ext_dep.yaml
create mode 100644 pip-requirements.txt
--
2.17.1
next reply other threads:[~2021-11-17 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 14:05 PierreGondois [this message]
2021-11-17 14:05 ` [PATCH edk2-platforms v6 1/6] pip-requirements.txt: Add python pip requirements file PierreGondois
2021-11-17 14:05 ` [PATCH edk2-platforms v6 2/6] CI: Add Tianocore edk2 as an external dependency PierreGondois
2021-11-17 14:05 ` [PATCH edk2-platforms v6 3/6] .pytool/Plugin: Add CI plugins PierreGondois
2021-11-17 14:05 ` [PATCH edk2-platforms v6 4/6] .azurepipelines: Add Azure Pipelines YML configuration files PierreGondois
2021-11-17 14:05 ` [PATCH edk2-platforms v6 5/6] .mergify: Add Mergify YML pull request rules configuration file PierreGondois
2021-11-17 14:05 ` [PATCH edk2-platforms v6 6/6] Platform/ARM: Juno: Add JunoPkg.ci.yaml for CI support PierreGondois
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=20211117140528.13600-1-Pierre.Gondois@arm.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