From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [for-next PATCH 1/2] Azure: Rework world build to directly use the container
Date: Wed, 26 Nov 2025 17:49:58 -0600 [thread overview]
Message-ID: <20251126234959.3909571-1-trini@konsulko.com> (raw)
While we had problems historically using buildman inside of a container
when invoked directly via Azure, rather than calling docker in our
script, that is no longer the case. We can make the job a bit easier to
understand by running it more normally. The challenge here is that our
container normally runs with an unprivileged user that we have populated
tools for and Azure creates and uses a new unprivileged user. Copy what
we need over to the new user.
Signed-off-by: Tom Rini <trini@konsulko.com>
---
.azure-pipelines.yml | 17 +++++++----------
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 0c7c38ba7300..8774af5393e3 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -613,6 +613,9 @@ stages:
displayName: 'Build the World'
pool:
vmImage: $(ubuntu_vm)
+ container:
+ image: $(ci_runner_image)
+ options: $(container_option)
strategy:
# We split the world up in to 10 jobs as we can have at most 10
# parallel jobs going on the free tier of Azure.
@@ -639,18 +642,15 @@ stages:
BUILDMAN: $(everything_but_arm_and_powerpc)
steps:
- script: |
- cat << EOF > build.sh
set -ex
- cd ${WORK_DIR}
- # make environment variables available as tests are running inside a container
- export BUILDMAN="${BUILDMAN}"
- git config --global --add safe.directory ${WORK_DIR}
+ # Copy things from /home/uboot to the Azure container user
+ sudo cp -a /home/uboot/.buildman /home/uboot/.cache ~
+ sudo chown -R 1001 ~/.cache ~/.buildman
+ # Setup venv, perform build
python3 -m venv /tmp/venv
. /tmp/venv/bin/activate
pip install -r tools/binman/requirements.txt \
-r tools/buildman/requirements.txt
- EOF
- cat << "EOF" >> build.sh
if [[ "${BUILDMAN}" != "" ]]; then
ret=0;
tools/buildman/buildman -o /tmp -PEWM ${BUILDMAN} ${OVERRIDE} || ret=$?;
@@ -659,6 +659,3 @@ stages:
exit $ret;
fi;
fi
- EOF
- cat build.sh
- docker run -v $PWD:$(work_dir) $(ci_runner_image) /bin/bash $(work_dir)/build.sh
--
2.43.0
next reply other threads:[~2025-11-26 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 23:49 Tom Rini [this message]
2025-11-26 23:49 ` [for-next PATCH 2/2] Azure: Rework binman testsuite job to directly use the container Tom Rini
2025-12-07 22:19 ` [for-next PATCH 1/2] Azure: Rework world build " 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=20251126234959.3909571-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