From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] ci: azure: Update to use stages
Date: Tue, 11 Jan 2022 19:14:28 -0500 [thread overview]
Message-ID: <20220112001431.1280749-1-trini@konsulko.com> (raw)
Follow what we do in GitLab CI where we break the jobs up in to stages
such that if earlier and often quicker sanity tests fail we don't run
everything else.
Signed-off-by: Tom Rini <trini@konsulko.com>
---
.azure-pipelines.yml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 670bbc0e1636..d97115668167 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -9,7 +9,9 @@ variables:
container_option: -u 0
work_dir: /u
-jobs:
+stages:
+- stage: testsuites
+ jobs:
- job: tools_only_windows
displayName: 'Ensure host tools build for Windows'
pool:
@@ -199,6 +201,8 @@ jobs:
export PATH=/opt/gcc-11.1.0-nolibc/arm-linux-gnueabi/bin:$PATH
test/nokia_rx51_test.sh
+- stage: test_py
+ jobs:
- job: test_py
displayName: 'test.py'
pool:
@@ -381,6 +385,8 @@ jobs:
# Some tests using libguestfs-tools need the fuse device to run
docker run "$@" --device /dev/fuse:/dev/fuse -v $PWD:$(work_dir) $(ci_runner_image) /bin/bash $(work_dir)/test.sh
+- stage: world_build
+ jobs:
- job: build_the_world
displayName: 'Build the World'
pool:
--
2.25.1
next reply other threads:[~2022-01-12 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 0:14 Tom Rini [this message]
2022-01-12 0:14 ` [PATCH 2/4] CI, Dockerfile: Update to latest "focal" tag Tom Rini
2022-01-12 1:55 ` Fabio Estevam
2022-01-12 1:56 ` Tom Rini
2022-01-13 12:53 ` Tom Rini
2022-01-12 0:14 ` [PATCH 3/4] binman: Have faked binaries live in the output directory Tom Rini
2022-01-12 20:01 ` Simon Glass
2022-01-12 20:03 ` Tom Rini
2022-01-12 20:11 ` Simon Glass
2022-01-12 0:14 ` [PATCH 4/4] .readthedocs.yml: Set our requirements file Tom Rini
2022-01-12 2:33 ` Heinrich Schuchardt
2022-01-12 22:05 ` [PATCH 1/4] ci: azure: Update to use stages Tom Rini
2022-01-13 12:53 ` Tom Rini
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=20220112001431.1280749-1-trini@konsulko.com \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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