From 89f4d07317266326e5f2c8442a1baa2a3a3bccbb Mon Sep 17 00:00:00 2001 From: Robert Schmidt Date: Wed, 24 Jan 2024 14:22:53 +0100 Subject: [PATCH] Don't delete ran-base at end of build Subsequent pipelines can/might use the ran-base image. Further, before building a new ran-base image, we delete it. Hence, it suffices to only delete the image when necessary (before building a new one), and otherwise leave the current (develop, ci-temp) ran-base image. --- ci-scripts/cls_containerize.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/ci-scripts/cls_containerize.py b/ci-scripts/cls_containerize.py index dceaf6a18a..09f77e1f76 100644 --- a/ci-scripts/cls_containerize.py +++ b/ci-scripts/cls_containerize.py @@ -505,8 +505,6 @@ class Containerize(): cmd.run(f"{self.cli} image prune --force") # Remove all intermediate build images and clean up - if self.ranAllowMerge and forceBaseImageBuild: - cmd.run(f"{self.cli} image rm {baseImage}:{baseTag}") cmd.run(f"{self.cli} image rm ran-build:{imageTag} ran-build-asan:{imageTag}") cmd.run(f"{self.cli} volume prune --force")