From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/3] gitlab-ci.yml: Add a job to build EDK2 firmware binaries
Date: Tue, 7 Jan 2020 12:35:50 +0100 [thread overview]
Message-ID: <505f9ed4-5b40-79d2-ac32-3ffb3d6c6976@redhat.com> (raw)
In-Reply-To: <74b5d03a-c3a3-38b8-68cb-192dd04f1802@redhat.com>
On 1/7/20 11:12 AM, Laszlo Ersek wrote:
> On 01/06/20 19:46, Philippe Mathieu-Daudé wrote:
>> Add a GitLab job to build the EDK2 firmware binaries.
>> This job is only built when the roms/edk2/ submodule is updated,
>> when a git-ref starts with 'edk2' or when the last commit contains
>> 'EDK2'.
>
> keyword "or"; okay.
>
>>
>> GitLab CI generates an artifacts.zip file containing the firmware
>> binaries.
>>
>> With edk2-stable201905, the job took 40 minutes 26 seconds,
>> the artifacts.zip takes 10MiB.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> .gitlab-ci-edk2.yml | 37 +++++++++++++++++++++++++++++++++++++
>> .gitlab-ci.yml | 3 +++
>> MAINTAINERS | 3 ++-
>> 3 files changed, 42 insertions(+), 1 deletion(-)
>> create mode 100644 .gitlab-ci-edk2.yml
>>
>> diff --git a/.gitlab-ci-edk2.yml b/.gitlab-ci-edk2.yml
>> new file mode 100644
>> index 0000000000..abfaf52874
>> --- /dev/null
>> +++ b/.gitlab-ci-edk2.yml
>> @@ -0,0 +1,37 @@
>> +build-edk2:
>> + rules: # Only run this job when ...
>> + - changes: # ... roms/edk2/ is modified (submodule updated)
>> + - roms/edk2/*
>> + when: always
>> + - if: '$CI_COMMIT_REF_NAME =~ /^edk2/' # ... the branch/tag starts with 'edk2'
>
> (1) can you add "or" in the comment here?
>
>> + when: always
>> + - if: '$CI_COMMIT_MESSAGE =~ /edk2/i' # last commit description contains 'EDK2'
>
> (2) ditto
>
>> + when: always
>> + artifacts:
>> + paths: # 'artifacts.zip' will contains the following files:
>> + - pc-bios/edk2*bz2
>> + - pc-bios/edk2-licenses.txt
>> + - edk2-stdout.log
>> + - edk2-stderr.log
>> + image: ubuntu:16.04 # Use Ubuntu Xenial
>> + before_script: # Install packages requiered to build EDK2
>> + - apt-get update --quiet --quiet
>> + - DEBIAN_FRONTEND=noninteractive
>> + apt-get install --assume-yes --no-install-recommends --quiet --quiet
>> + build-essential
>> + ca-certificates
>> + dos2unix
>> + gcc-aarch64-linux-gnu
>> + gcc-arm-linux-gnueabi
>> + git
>> + iasl
>> + make
>> + nasm
>> + python
>> + uuid-dev
>> + script: # Clone the required submodules and build EDK2
>> + - git submodule update --init roms/edk2
>
> yes, this is needed; qemu users are used to updating top-level
> submodules (which is why we didn't try to automate that away in the edk2
> build stuff)
>
>> + - git -C roms/edk2 submodule update --init
>
> (3) but this should not be necessary. See the "submodules" target in
> "roms/Makefile.edk2".
Hmm build fails without it:
https://gitlab.com/philmd/qemu/-/jobs/395644357#L436
The 'test -d edk2/.git' might be not enough?
>> + - export JOBS=$(($(getconf _NPROCESSORS_ONLN) + 1))
>> + - echo "=== Using ${JOBS} simultaneous jobs ==="
>> + - make -j${JOBS} -C roms efi 1>edk2-stdout.log 2> >(tee -a edk2-stderr.log >&2)
>
> Process substitution is a nifty feature, but perhaps we can do without
> it, for simplicity. (I realize this is bash-only; I just like to
> minimize the use of non-portable features if there is a portable
> replacement that is also simple.)
>
> Redirections are processed in the order they appear on the command line
> [1], *after* stdout/stdin is redirected for pipelining [2]:
>
> [1]
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07
>
> "If more than one redirection operator is specified with a command, the
> order of evaluation is from beginning to end."
>
> [2]
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_02
>
> "The standard input, standard output, or both of a command shall be
> considered to be assigned by the pipeline before any redirection
> specified by redirection operators that are part of the command"
>
>
> (4) Therefore, the following should work:
>
> make -j${JOBS} -C roms efi 2>&1 1>edk2-stdout.log \
> | tee -a edk2-stderr.log >&2
>
> Untested, of course :)
This works like charm :>
> Looks OK otherwise.
Thanks for the review!
>
> Thanks!
> Laszlo
next prev parent reply other threads:[~2020-01-07 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 18:45 [PATCH 0/3] gitlab-ci: Add a job to build EDK2 firmware binaries Philippe Mathieu-Daudé
2020-01-06 18:45 ` [PATCH 1/3] roms/edk2-funcs: Force softfloat ARM toolchain prefix on Debian Philippe Mathieu-Daudé
2020-01-07 9:41 ` Laszlo Ersek
2020-01-06 18:46 ` [PATCH 2/3] gitlab-ci.yml: Add a job to build EDK2 firmware binaries Philippe Mathieu-Daudé
2020-01-07 7:48 ` Philippe Mathieu-Daudé
2020-01-07 10:12 ` Laszlo Ersek
2020-01-07 11:35 ` Philippe Mathieu-Daudé [this message]
2020-01-07 18:55 ` Laszlo Ersek
2020-01-06 18:46 ` [PATCH 3/3] gitlab-ci-edk2.yml: Use ccache Philippe Mathieu-Daudé
2020-01-07 10:19 ` Laszlo Ersek
2020-01-07 10:23 ` Philippe Mathieu-Daudé
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-all 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=505f9ed4-5b40-79d2-ac32-3ffb3d6c6976@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).