[libcxx-commits] [libcxx] d6bfedd - [libc++] Remove dummy command in Dockerfile
Louis Dionne via libcxx-commits
libcxx-commits at lists.llvm.org
Mon Jun 27 06:17:38 PDT 2022
Author: Louis Dionne
Date: 2022-06-27T09:17:34-04:00
New Revision: d6bfedd8ba73f2c8cf51f0548ff98b2041b25733
URL: https://github.com/llvm/llvm-project/commit/d6bfedd8ba73f2c8cf51f0548ff98b2041b25733
DIFF: https://github.com/llvm/llvm-project/commit/d6bfedd8ba73f2c8cf51f0548ff98b2041b25733.diff
LOG: [libc++] Remove dummy command in Dockerfile
It turns out that the Docker images on CI instances are not updated
based on what's in this file, but instead when a new image is pushed
to ldionne/libcxx-builder on DockerHub. So this is effectively useless.
Added:
Modified:
libcxx/utils/ci/Dockerfile
Removed:
################################################################################
diff --git a/libcxx/utils/ci/Dockerfile b/libcxx/utils/ci/Dockerfile
index 76cb22476a617..f175b705e3b9e 100644
--- a/libcxx/utils/ci/Dockerfile
+++ b/libcxx/utils/ci/Dockerfile
@@ -33,12 +33,6 @@ FROM ubuntu:jammy
# Make sure apt-get doesn't try to prompt for stuff like our time zone, etc.
ENV DEBIAN_FRONTEND=noninteractive
-# This dummy command is meant to be edited from time to time, which causes the
-# CI builders to rebuild their copy of the Docker image. This is not a great
-# solution, however without that, the CI builders will keep the same cached
-# Docker image forever.
-RUN echo 6
-
RUN apt-get update && apt-get install -y bash curl
# Install various tools used by the build or the test suite
More information about the libcxx-commits
mailing list