Details
-
Sub-task
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
statefun-2.0.0
Description
If we choose to use Travis, setting this up should be fairly straightforward.
On the other hand, if we choose to use Azure Pipelines to be consistent with the community's recent discussion to migrate from Travis to Azure Pipelines for apache/flink, things will be a bit more complicated.
As with apache/flink's integration with Azure Pipelines, there is a problem with Azure Pipelines requiring write access for a proper integration, which ASF does not allow.
Therefore, for Stateful Functions we also need to follow the approach that all branches / PR are mirrored to a CI repository not managed by ASF, on which Azure Pipelines monitors.
The proposed concrete steps for setting this up for Stateful Functions with Azure Pipelines is as follows:
- Add a minimal azure-pipelines.yml to apache/flink-statefun that runs containerized builds with JDK 8 and JDK 11. Stateful Functions should not require a custom container for the CI build environment, for now. The official Maven images maven:3.x.x-jdk-8/11 should be sufficient for our current needs.
- Request a new "ci repository" at flink-ci/flink-statefun. Setup Azure Pipelines for the ci repository.
- Setup a CIBot instance to observe on apache/flink-statefun, replicate to flink-ci/flink-statefun, and reports back build checks to apache/flink-statefun. We should be able to reuse flink-ci/ci-bot, probably with a change that allows it to run without a Travis auth token (because Stateful Functions would not have Travis integration from the beginning).
- Update project wiki with details on the setup.
We need to reach out to Ververica for steps 2. and 3, since the current CI repo flink-ci and the CIBot instances are managed by them.
Attachments
Issue Links
- is blocked by
-
FLINK-15842 Building Stateful Functions with JDK 11 fails due to outdated Spotbugs version
- Closed
- links to