Matthias Pohl created FLINK-33214:
-------------------------------------
Summary: Moving away from the Ververica-owned S3 bucket and use
Apache Infra's nightly SVN instead
Key: FLINK-33214
URL: https://issues.apache.org/jira/browse/FLINK-33214
Project: Flink
Issue Type: Technical Debt
Components: Build System
Reporter: Matthias Pohl
Currently, we're deploying snapshot versions of Flink to a Ververica-owned S3
bucket. Instead, it's recommended to use Apache Infra resources with
https://nightlies.apache.org/flink/, instead.
It was verified with Apache Infra that the capacity of the repository would
work for Flink's nightly (see [Slack
post|https://the-asf.slack.com/archives/CBX4TSBQ8/p1696357867690409] and
follow-ups).
{quote}
Martijn Visser: Hi all, I wanted to double check if it's safe to use
https://nightlies.apache.org/flink/ for storing nightly builds of Apache Flink,
which are created after a successful merge. We use these in weekly runs of
Apache Flink connectors (that all reside in their own repository), where we
test that connector against the snapshot version that's available. We cache the
binaries in Flink connector runs, to avoid overly downloading them.
---
Gavin McDonald: sure, hopefully size isnt excessive
---
Martijn Visser: flink-1.18-SNAPSHOT-bin-scala_2.12.tgz (size: 478MB)
:sweat_smile:
---
Gavin McDonald: let me look into it further, remind myself what space we have
etc. will report back tomorrow
---
Chesnay Schepler: FWIW we'd need (exactly) 3 of these files at any given time,
right
@Martijn Visser? Last 2 versions + master.
---
Martijn Visser: Yes, correct
---
Gavin McDonald: ok I think we should be fine
{quote}
(!) Moving to SVN for nightly storage also includes updating the release
documentation: We have to clean up deprecated minor version snapshots to keep
the memory footprint low.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
