[
https://issues.apache.org/jira/browse/FLINK-34695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827500#comment-17827500
]
Matthias Pohl commented on FLINK-34695:
---------------------------------------
This should be discussed in the dev ML before going ahead with the change, I
guess. ...if someone wants to pick this up.
> Move Flink's CI docker container into a public repo
> ---------------------------------------------------
>
> Key: FLINK-34695
> URL: https://issues.apache.org/jira/browse/FLINK-34695
> Project: Flink
> Issue Type: Improvement
> Components: Build System / CI
> Affects Versions: 1.19.0, 1.18.1, 1.20.0
> Reporter: Matthias Pohl
> Priority: Major
>
> Currently, Flink's CI (GitHub Actions and Azure Pipelines) use a container to
> run the logic. The intention behind it is to have a way to mimick the CI
> setup locally as well.
> The current Docker image is maintained from the
> [zentol/flink-ci-docker|https://github.com/zentol/flink-ci-docker] fork
> (owned by [~chesnay]) of
> [flink-ci/flink-ci-docker|https://github.com/flink-ci/flink-ci-docker] (owned
> by Ververica) which is not ideal. We should move this repo into a
> Apache-owned repository.
> Additionally, the there's no workflow pushing the image automatically to a
> registry from where it can be used. Instead, the images were pushed to
> personal Docker Hub repos in the past (rmetzger, chesnay, mapohl). This is
> also not ideal. We should use a public repo using a GHA workflow to push the
> image to that repo.
> Questions to answer here:
> # Where shall the Docker image code be located?
> # Which Docker registry should be used?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
