[
https://issues.apache.org/jira/browse/FLINK-18643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162765#comment-17162765
]
Chesnay Schepler commented on FLINK-18643:
------------------------------------------
??For a nightly "binary release", we could just upload them as a build artifact
(finding that file will be insanely difficult for our users though).
Alternatively, we keep uploading them to s3 (from Azure).??
That is fine since we are not allowed to advertise snapshot binaries to _users_
anyway. The only people that should be able to find it are developers, and
there we can be as obtuse as we want.
??If we want to continue, Azure DevOps has a module called "Artifacts", that
also seems to support Maven[...]??
We'd have to check whether we are allowed to put ASF credentials into a non-ASF
managed Azure account. That is, if we want to publish to the ASF snapshot
repository (which I suppose we do want).
??I'm not sure how many people are really using the snapshot versions we are
deploying.??
I use them personally, and would suspect that other developers do too.
The snapshot binaries are also required for ensuring that the docker images are
compatible with the upcoming Flink version.
> Migrate Jenkins jobs to ci-builds.apache.org
> --------------------------------------------
>
> Key: FLINK-18643
> URL: https://issues.apache.org/jira/browse/FLINK-18643
> Project: Flink
> Issue Type: Improvement
> Components: Release System
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
>
> Infra is [reworking the Jenkins
> setup|https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E],
> so we have to migrate our jobs that do the snapshot deployments.
> Alternatively, find other ways to do this (Azure?) to reduce number of used
> infrastructure services.
> /cc [~rmetzger]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
