You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/04/05 11:59:00 UTC
[jira] [Updated] (FLINK-11786) Merge cron branches into respective
release branches
[ https://issues.apache.org/jira/browse/FLINK-11786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler updated FLINK-11786:
-------------------------------------
Fix Version/s: (was: 1.8.1)
(was: 1.9.0)
1.8.0
> Merge cron branches into respective release branches
> ----------------------------------------------------
>
> Key: FLINK-11786
> URL: https://issues.apache.org/jira/browse/FLINK-11786
> Project: Flink
> Issue Type: Improvement
> Components: Travis
> Affects Versions: 1.7.2, 1.8.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.3, 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Apparently it is possible for jobs to have distinct {{script}} entries without affecting the caching (which we need for our stage setup to work). This allows us to merge all cron branches into the respective release branch.
> So far we couldn't do it since we relied on the order of jobs to determine what a particular job should be doing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)