You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/02/03 03:37:00 UTC

[jira] [Issue Comment Deleted] (FLINK-15850) Setup CI for Stateful Functions with Azure Pipelines

     [ https://issues.apache.org/jira/browse/FLINK-15850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tzu-Li (Gordon) Tai updated FLINK-15850:
----------------------------------------
    Comment: was deleted

(was: cc [~rmetzger] [~chesnay])

> Setup CI for Stateful Functions with Azure Pipelines
> ----------------------------------------------------
>
>                 Key: FLINK-15850
>                 URL: https://issues.apache.org/jira/browse/FLINK-15850
>             Project: Flink
>          Issue Type: Task
>          Components: Stateful Functions, Test Infrastructure
>    Affects Versions: statefun-1.1
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Blocker
>
> Stateful Functions ({{apache/flink-statefun}}) is still lacking a CI setup.
> Since the community recently agreed on eventually migrating to Azure Pipelines for our CI builds, we propose to initially use that to setup CI for Stateful Functions as well.
> This is an umbrella ticket to track individual subtasks.
> The end goal for the setup is:
> * CI pipeline that covers builds for JDK 8 and 11, also with end-to-end test coverage (both builds and e2e are initially run per push / per PR)
> * Pipeline integrated with flinkbot so that build check results are reported back to PRs in {{apache/flink-statefun}}. The same problem with Azure Pipelines requiring write access for proper integration, as is with {{apache/flink}}, also exists here.
> * Update project wiki with the CI pipeline details for {{apache/flink-statefun}}



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