[
https://issues.apache.org/jira/browse/FLINK-15850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tzu-Li (Gordon) Tai updated FLINK-15850:
----------------------------------------
Description:
Stateful Functions ({{apache/flink-statefun}}) is still lacking a CI setup.
We should look at setting this up with either Travis or Azure Pipelines.
Travis would be fairly straightforward to setup with the current usage needs of
the Stateful Functions repo, while Azure Pipelines is the solution that the
Flink community recently agreed on eventually migrating to for CI on
{{apache/flink}}.
This is an umbrella ticket to track individual subtasks.
The end goal for the setup is:
* CI jobs that covers builds for JDK 8 and 11,
* CI jobs with end-to-end test coverage (Stateful Functions would probably rely
on docker / docker-compose for its end-to-end tests)
* Update project wiki with the CI pipeline details for {{apache/flink-statefun}}
was:
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}}
> Setup CI for Stateful Functions
> -------------------------------
>
> 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.
> We should look at setting this up with either Travis or Azure Pipelines.
> Travis would be fairly straightforward to setup with the current usage needs
> of the Stateful Functions repo, while Azure Pipelines is the solution that
> the Flink community recently agreed on eventually migrating to for CI on
> {{apache/flink}}.
> This is an umbrella ticket to track individual subtasks.
> The end goal for the setup is:
> * CI jobs that covers builds for JDK 8 and 11,
> * CI jobs with end-to-end test coverage (Stateful Functions would probably
> rely on docker / docker-compose for its end-to-end tests)
> * Update project wiki with the CI pipeline details for
> {{apache/flink-statefun}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
