[
https://issues.apache.org/jira/browse/FLINK-33175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773144#comment-17773144
]
Matthias Pohl commented on FLINK-33175:
---------------------------------------
> It just uses a plain wget to download the Flink binary from S3, so I guess
> the assumption on connector side is that the binary should be public
> accessible (please correct me if I'm wrong Martijn Visser).
That was also my conclusion. Based on [~rmetzger]'s memory the corresponding S3
Bucket is a legacy resource that might be owned by Ververica. I would think
that one should connect to the S3 bucket and check the permissions.
I talked to [~mdedetrich] (from Apache Pekko) about nightly builds: The
conclusion was that we might want to use the nightly SVN repo
(https://nightlies.apache.org/flink/) which is provided by Apache INFRA.
Apparently, that's the intended way of deploying nightlies in the Apache world.
We're using it already for the docs nightlies. In that case, infra would be
hosting the storage. That might reduce the burden on Ververica's/Alibaba's
side. But we might want to discuss it on the mailing list first and create a
follow-up issue for that one.
> Nightly builds from S3 are not available for download, breaking all connector
> tests
> -----------------------------------------------------------------------------------
>
> Key: FLINK-33175
> URL: https://issues.apache.org/jira/browse/FLINK-33175
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Common
> Reporter: Martijn Visser
> Priority: Blocker
>
> All downloads of Flink binaries fail with:
> {code:java}
> Run wget -q -c
> https://s3.amazonaws.com/flink-nightly/flink-1.18-SNAPSHOT-bin-scala_2.12.tgz
> -O - | tar -xz
> gzip: stdin: unexpected end of file
> tar: Child returned status 1
> tar: Error is not recoverable: exiting now
> Error: Process completed with exit code 2.
> {code}
> This goes for 1.18, but also 1.17 and 1.16
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
