autophagy opened a new pull request #16332:
URL: https://github.com/apache/flink/pull/16332
## What is the purpose of the change
There has been a lot of flakiness in the testing infrastructure around the
use of docker containers, specifically testcontainers. We think this might be
due to the introduction of pull rate-limits on Dockerhub docker images back in
November 2020.
This PR caches dockerfiles pulled during the testing in order to reduce the
number of pull requests made against Dockerhub, and each testing module
maintains its own cache, as different testing modules may rely on different
containers. With this caching strategy, the connectors test module caches the
following docker images:
- debian:10
- node:10-alpine
- node:10
- rmetzger/flink-ci:ubuntu-amd64-7ac4e28
- testcontainers/ryuk:0.3.1
- rabbitmq:3.7.25-management-alpine
- ubuntu:16.04
- ubuntu:18.04
- buildpack-deps:stretch
- docker.elastic.co/elasticsearch/elasticsearch-oss:6.3.1
- node:14
- node:14-alpine
- ubuntu:20.04
- node:12-alpine
- alpine:3.11
- mysql:8.0.23
- instructure/kinesalite:latest
- debian:9
- alpine:3.12
- alpine:3.13
- testcontainers/ryuk:0.3.0
- docker.elastic.co/elasticsearch/elasticsearch-oss:7.5.1
- postgres:9.6.12
- node:12
- buildpack-deps:buster
Perhaps a subset of these would be more appropriate, such as the non-base
images. I was also unsure as to what the appropriate cache key would be for
this, or whether a dynamic cache key would make much sense at all.
## Brief change log
- *A cache for Docker images used during CI testing has been introduced*
## Verifying this change
This change is already covered by existing tests, such as *(please describe
tests)*.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
- The S3 file system connector: (no)
## Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable)
--
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]
