From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Kyle Evans" <kevans@freebsd.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <willianr@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Warner Losh" <imp@bsdimp.com>
Subject: [PATCH v3 1/6] gitlab-ci: Extract &environment_variables template
Date: Wed, 19 May 2021 20:45:44 +0200 [thread overview]
Message-ID: <20210519184549.2192728-2-f4bug@amsat.org> (raw)
In-Reply-To: <20210519184549.2192728-1-f4bug@amsat.org>
To be able to set the same environment variables to multiple jobs,
extract what we currently have as a template.
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
.gitlab-ci.d/buildtest-template.yml | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci.d/buildtest-template.yml b/.gitlab-ci.d/buildtest-template.yml
index 32aaef1a213..58b01744751 100644
--- a/.gitlab-ci.d/buildtest-template.yml
+++ b/.gitlab-ci.d/buildtest-template.yml
@@ -1,8 +1,11 @@
+.environment_variables_template:
+ before_script:
+ - JOBS=$(expr $(nproc) + 1)
+
.native_build_job_template:
stage: build
image: $CI_REGISTRY_IMAGE/qemu/$IMAGE:latest
- before_script:
- - JOBS=$(expr $(nproc) + 1)
+ extends: .environment_variables_template
script:
- if test -n "$LD_JOBS";
then
--
2.26.3
next prev parent reply other threads:[~2021-05-19 19:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 18:45 [PATCH v3 0/6] gitlab-ci: Allow using FreeBSD runners Philippe Mathieu-Daudé
2021-05-19 18:45 ` Philippe Mathieu-Daudé [this message]
2021-05-19 19:12 ` [PATCH v3 1/6] gitlab-ci: Extract &environment_variables template Willian Rampazzo
2021-05-20 18:00 ` Wainer dos Santos Moschetta
2021-05-19 18:45 ` [PATCH v3 2/6] gitlab-ci: Adapt JOBS variable for FreeBSD runners Philippe Mathieu-Daudé
2021-05-19 19:11 ` Willian Rampazzo
2021-05-20 5:50 ` Thomas Huth
2021-05-20 18:18 ` Wainer dos Santos Moschetta
2021-05-20 20:02 ` Warner Losh
2021-05-19 18:45 ` [PATCH v3 3/6] gitlab-ci: Run GNU make via the $MAKE variable Philippe Mathieu-Daudé
2021-05-19 19:10 ` Willian Rampazzo
2021-05-20 7:56 ` Thomas Huth
2021-05-20 18:26 ` Wainer dos Santos Moschetta
2021-05-19 18:45 ` [PATCH v3 4/6] gitlab-ci: Add ccache in $PATH and display statistics Philippe Mathieu-Daudé
2021-05-19 19:14 ` Willian Rampazzo
2021-05-20 8:02 ` Thomas Huth
2021-05-20 11:27 ` Philippe Mathieu-Daudé
2021-05-21 10:48 ` Thomas Huth
2021-05-21 10:50 ` Daniel P. Berrangé
2021-05-21 11:02 ` Thomas Huth
2021-05-21 11:53 ` Daniel P. Berrangé
2021-05-21 12:27 ` Philippe Mathieu-Daudé
2021-05-21 12:52 ` Daniel P. Berrangé
2021-05-21 14:21 ` Philippe Mathieu-Daudé
2021-05-25 5:49 ` Philippe Mathieu-Daudé
2021-05-24 13:51 ` Stefan Hajnoczi
2021-05-25 5:50 ` Philippe Mathieu-Daudé
2021-05-21 12:36 ` Willian Rampazzo
2021-05-21 13:02 ` Thomas Huth
2021-05-19 18:45 ` [PATCH v3 5/6] gitlab-ci: Simplify before/after script for Avocado based jobs Philippe Mathieu-Daudé
2021-05-19 19:42 ` Willian Rampazzo
2021-05-20 8:04 ` Thomas Huth
2021-05-19 18:45 ` [PATCH v3 6/6] gitlab-ci: Add FreeBSD jobs Philippe Mathieu-Daudé
2021-05-19 19:43 ` Willian Rampazzo
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=20210519184549.2192728-2-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@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).