From: "PierreGondois" <pierre.gondois@arm.com>
To: devel@edk2.groups.io, 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 v3 0/6] Enable edk2-platforms CI for JunoPkg
Date: Fri, 30 Jul 2021 14:15:43 +0100 [thread overview]
Message-ID: <20210730131549.26198-1-Pierre.Gondois@arm.com> (raw)
From: Pierre Gondois <Pierre.Gondois@arm.com>
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
This patch-set is dependent on the following patch-set:
edk2-platforms:
[PATCH v1 0/2] Fix duplicated GUID
https://edk2.groups.io/g/devel/message/76910
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 aswel.
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.
Compared to edk2's CI, an additional step has been added to checkout
edk2's latest master. Indeed, some changes in the edk2-platforms
repository might rely on modifications in the edk2 repository.
The policy here would be to have edk2's repository's modifications
accepted first so edk2-platforms's CI can complete successfully.
As the new edk2 submodule is updated to the latest master when running
the CI, this still raises the question of when to update this new edk2
submodule.
The changes can be seen at:
https://github.com/PierreARM/edk2-platforms/tree/1628_Enable_edk2_platforms_ci_for_JunoPkg_v3
Pierre Gondois (6):
edk2-platforms: add edk2 repository as a submodule
pip-requirements.txt: Add python pip requirements file
.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 | 20 ++
.azurepipelines/Ubuntu-PatchCheck.yml | 36 ++++
.azurepipelines/Windows-VS2019.yml | 20 ++
.azurepipelines/templates/ReadMe.md | 5 +
.../templates/basetools-build-steps.yml | 37 ++++
.../templates/platform-build-run-steps.yml | 151 ++++++++++++++
.../templates/pr-gate-build-job.yml | 43 ++++
.azurepipelines/templates/pr-gate-steps.yml | 149 ++++++++++++++
.../templates/spell-check-prereq-steps.yml | 22 +++
.gitmodules | 3 +
.mergify/config.yml | 50 +++++
.pytool/CISettings.py | 184 ++++++++++++++++++
.pytool/Readme.md | 25 +++
Platform/ARM/JunoPkg/JunoPkg.ci.yaml | 104 ++++++++++
edk2 | 1 +
pip-requirements.txt | 18 ++
17 files changed, 873 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/basetools-build-steps.yml
create mode 100644 .azurepipelines/templates/platform-build-run-steps.yml
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 160000 edk2
create mode 100644 pip-requirements.txt
--
2.17.1
next reply other threads:[~2021-07-30 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 13:15 PierreGondois [this message]
2021-07-30 13:15 ` [PATCH edk2-platforms v3 1/6] edk2-platforms: add edk2 repository as a submodule PierreGondois
2021-07-30 13:15 ` [PATCH edk2-platforms v3 2/6] pip-requirements.txt: Add python pip requirements file PierreGondois
2021-07-30 13:15 ` [PATCH edk2-platforms v3 3/6] .pytool/Plugin: Add CI plugins PierreGondois
2021-07-30 13:15 ` [PATCH edk2-platforms v3 4/6] .azurepipelines: Add Azure Pipelines YML configuration files PierreGondois
2021-07-30 13:15 ` [PATCH edk2-platforms v3 5/6] .mergify: Add Mergify YML pull request rules configuration file PierreGondois
2021-07-30 13:15 ` [PATCH edk2-platforms v3 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=20210730131549.26198-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