From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/4] CI, Dockerfile: Update to latest "focal" tag
Date: Tue, 11 Jan 2022 19:14:29 -0500 [thread overview]
Message-ID: <20220112001431.1280749-2-trini@konsulko.com> (raw)
In-Reply-To: <20220112001431.1280749-1-trini@konsulko.com>
Bring us to the focial-20220105 tag and rebuild our images on top of
this.
Signed-off-by: Tom Rini <trini@konsulko.com>
---
.azure-pipelines.yml | 2 +-
.gitlab-ci.yml | 2 +-
tools/docker/Dockerfile | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index d97115668167..c0f72a811363 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -2,7 +2,7 @@ variables:
windows_vm: windows-2019
ubuntu_vm: ubuntu-18.04
macos_vm: macOS-10.15
- ci_runner_image: trini/u-boot-gitlab-ci-runner:focal-20211006-14Nov2021
+ ci_runner_image: trini/u-boot-gitlab-ci-runner:focal-20220105-10Jan2022
# Add '-u 0' options for Azure pipelines, otherwise we get "permission
# denied" error when it tries to "useradd -m -u 1001 vsts_azpcontainer",
# since our $(ci_runner_image) user is not root.
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index d06cca45fd04..4c44c01e7bf5 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -2,7 +2,7 @@
# Grab our configured image. The source for this is found at:
# https://source.denx.de/u-boot/gitlab-ci-runner
-image: trini/u-boot-gitlab-ci-runner:focal-20211006-14Nov2021
+image: trini/u-boot-gitlab-ci-runner:focal-20220105-10Jan2022
# We run some tests in different order, to catch some failures quicker.
stages:
diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
index fb422e758813..f19e618ffba3 100644
--- a/tools/docker/Dockerfile
+++ b/tools/docker/Dockerfile
@@ -2,7 +2,7 @@
# This Dockerfile is used to build an image containing basic stuff to be used
# to build U-Boot and run our test suites.
-FROM ubuntu:focal-20211006
+FROM ubuntu:focal-20220105
MAINTAINER Tom Rini <trini@konsulko.com>
LABEL Description=" This image is for building U-Boot inside a container"
--
2.25.1
next prev parent 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 [PATCH 1/4] ci: azure: Update to use stages Tom Rini
2022-01-12 0:14 ` Tom Rini [this message]
2022-01-12 1:55 ` [PATCH 2/4] CI, Dockerfile: Update to latest "focal" tag 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-2-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