[
https://issues.apache.org/jira/browse/FLINK-18643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180565#comment-17180565
]
Robert Metzger edited comment on FLINK-18643 at 8/19/20, 1:49 PM:
------------------------------------------------------------------
I haven't considered this, but yes, I'm able to backport the changes to 1.11
easily. I would push the change once the nightly creation has worked on master
(it didn't last night, which was the first night (fixed))
For 1.10, my strategy would be "hope". If somebody really needs a snapshot
build, they need to build it themselves, or we manually deploy one. But I'm not
sure if it is worth the effort, without any known users.
Are you okay with removing the build configuration from Jenkins now?
was (Author: rmetzger):
I haven't considered this, but yes, I'm able to backport the changes to 1.11
easily.
For 1.10, my strategy would be "hope". If somebody really needs a snapshot
build, they need to build it themselves, or we manually deploy one. But I'm not
sure if it is worth the effort, without any known users.
Are you okay with removing the build configuration from Jenkins now?
> 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: Robert Metzger
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> 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)
