zentol commented on a change in pull request #16332:
URL: https://github.com/apache/flink/pull/16332#discussion_r668516619



##########
File path: tools/azure-pipelines/cache_docker_images.sh
##########
@@ -0,0 +1,56 @@
+#!/usr/bin/env bash
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+
+#
+# To reduce the number of pull requests we make against dockerhub, this script
+# saves the docker images we typically pull during a testing cycle. This 
typically
+# includes testcontainer images, kafka, elasticearch, etc.
+#
+echo 
"=============================================================================="
+echo "Caching Testing Docker Images"
+echo 
"=============================================================================="
+echo ""
+
+if [ -z "$TESTCONTAINER_CACHE_FOLDER" ]
+then
+      echo "\$TESTCONTAINER_CACHE_FOLDER must be set to cache the testing 
docker images. Exiting"
+      exit 1
+fi
+
+mkdir -p "${TESTCONTAINER_CACHE_FOLDER}"
+
+# This is the pattern that determines which containers we save.
+DOCKER_IMAGE_CACHE_PATTERN="testcontainers|kafka|elasticsearch|postgres|mysql"

Review comment:
       Nothing we need to fix now, but long-term it could be neat to derive 
this from `TestContainerVersions.java`.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to