[dunfell] CI: use the latest release of the Kas container

Message ID 20220128191907.2767570-1-ross.burton@arm.com
State New
Headers show
Series [dunfell] CI: use the latest release of the Kas container | expand

Commit Message

Ross Burton Jan. 28, 2022, 7:19 p.m. UTC
If we don't specify a tag name GitLab uses the 'latest' tag, which for
Kas is moved whenever an image build is made.

Instead explicitly use the latest-release tag, which is only updated
when a release is made.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Jon Mason Jan. 29, 2022, 12:01 a.m. UTC | #1
On Fri, 28 Jan 2022 19:19:07 +0000, Ross Burton wrote:
> If we don't specify a tag name GitLab uses the 'latest' tag, which for
> Kas is moved whenever an image build is made.
> 
> Instead explicitly use the latest-release tag, which is only updated
> when a release is made.

Applied, thanks!

[1/1] CI: use the latest release of the Kas container
      commit: 3a2b7d55c7fdfd80e2f8c23d07b4217293c6b050

Best regards,

Patch

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 1bf02702..134b50a2 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@ 
-image: ghcr.io/siemens/kas/kas
+image: ghcr.io/siemens/kas/kas:latest-release
 
   # First do a common bootstrap, and then build all the targets
 stages: