From: Romain Naour <romain.naour@gmail.com>
To: buildroot@buildroot.org
Cc: Romain Naour <romain.naour@gmail.com>
Subject: [Buildroot] [PATCH 2/3] gitlab-ci.yml: add stage explicitely to each jobs
Date: Mon, 17 Jul 2023 23:33:58 +0200 [thread overview]
Message-ID: <20230717213359.106368-2-romain.naour@gmail.com> (raw)
In-Reply-To: <20230717213359.106368-1-romain.naour@gmail.com>
"stages" is curently not defined in the .gitlab-ci.yml file,
so the default pipeline stages are:
.pre
build
test
deploy
.post
Since any jobs specify a stage, all jobs are assigned the "test"
stage [1]. All other stages defined by default are not used in the
gitlab-ci pipeline, they remain hidden.
In order to introduce a new custom stage, add the "test" stage
explicitely.
[1] https://docs.gitlab.com/ee/ci/yaml/#stages
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
support/misc/gitlab-ci.yml.in | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/support/misc/gitlab-ci.yml.in b/support/misc/gitlab-ci.yml.in
index cbb6e555ce..d8d6b3f410 100644
--- a/support/misc/gitlab-ci.yml.in
+++ b/support/misc/gitlab-ci.yml.in
@@ -1,27 +1,36 @@
+stages:
+ - test
+
before_script:
- git config --global --add safe.directory ${CI_PROJECT_DIR}
.check-check-package_base:
+ stage: test
script:
- python3 -m pytest -v utils/checkpackagelib/
.check-check-symbol_base:
+ stage: test
script:
- python3 -m pytest -v utils/checksymbolslib/
.check-DEVELOPERS_base:
+ stage: test
script:
- utils/get-developers -v
.check-package_base:
+ stage: test
script:
- make check-package
.check-symbol_base:
+ stage: test
script:
- utils/check-symbols
.defconfig_check:
+ stage: test
script:
- DEFCONFIG_NAME=$(echo ${CI_JOB_NAME} | sed -e 's,_check$,,g')
- echo "Configure Buildroot for ${DEFCONFIG_NAME}"
@@ -42,6 +51,7 @@ before_script:
}
.defconfig_base:
+ stage: test
script:
- DEFCONFIG_NAME=${CI_JOB_NAME}
- OUTPUT_DIR=output
@@ -69,6 +79,7 @@ before_script:
- runtime-test.log
.runtime_test_base:
+ stage: test
# Keep build directories so the rootfs can be an artifact of the job. The
# runner will clean up those files for us.
# Multiply every emulator timeout by 10 to avoid sporadic failures in
@@ -86,7 +97,7 @@ before_script:
- test-output/*/images/*
.test_pkg:
- stage: build
+ stage: test
script:
- OUTPUT_DIR=${CI_JOB_NAME}
- echo "Configure Buildroot for ${OUTPUT_DIR}"
--
2.41.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-17 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 21:33 [Buildroot] [PATCH 1/3] support/run-tests: add a mode to only download emulator builtin binaries Romain Naour
2023-07-17 21:33 ` Romain Naour [this message]
2023-07-17 21:33 ` [Buildroot] [PATCH 3/3] gitlab-ci.yml: pass emulator builtin binaries as artifacts Romain Naour
2023-07-18 21:05 ` [Buildroot] [PATCH 1/3] support/run-tests: add a mode to only download emulator builtin binaries Thomas Petazzoni via buildroot
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=20230717213359.106368-2-romain.naour@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@buildroot.org \
/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