You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/01/31 11:17:00 UTC

[jira] [Commented] (FLINK-13978) Switch to Azure Pipelines as a CI tool for Flink

    [ https://issues.apache.org/jira/browse/FLINK-13978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027417#comment-17027417 ] 

Till Rohrmann commented on FLINK-13978:
---------------------------------------

Please close FLINK-8745 once this issue is resolved.

> Switch to Azure Pipelines as a CI tool for Flink
> ------------------------------------------------
>
>                 Key: FLINK-13978
>                 URL: https://issues.apache.org/jira/browse/FLINK-13978
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> See ML discussion: [https://lists.apache.org/thread.html/b90aa518fcabce94f8e1de4132f46120fae613db6e95a2705f1bd1ea@%3Cdev.flink.apache.org%3E] 
> We want to try out Azure Pipelines for the following reasons:
>  * more mature system (compared to travis)
>  * 10 parallel, 6 hrs builds for open source
>  * ability to add custom machines
>  
> (See also INFRA-17030) 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)