[
https://issues.apache.org/jira/browse/FLINK-13646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902817#comment-16902817
]
wangxiyuan commented on FLINK-13646:
------------------------------------
Hi Stephan
All scripts will be in Flink repo.
openlab/flink repo is just forked for POC. This repo will be deleted once
apache/flink ARM CI start working.
What will be added to Flink repo:
# A *.zuul.yaml* file. It's used for defining what kind of job should be ran.
(like the *.travis.yml* file)
# some jobs execution yaml files. They contains the job detail that what
commands and scripts will be ran. (like the .sh file in tools/travis)
Since all files will be in Flink repo, it's easy and fast for Flink forks to
change and maintian them. Don't need any dependence on openlab repo.
It's quite similar with tarvis-ci. The difference is only that tarvis executes
.sh file direclty on X86 but openlab-ci executes ansible scripts on either X86
or ARM.
Once it's done, you can find the CI report in each PR at the same level with
travis-ci.
[An containerd PR example|https://github.com/containerd/containerd/pull/2918]
> Add ARM CI job definition scripts
> ---------------------------------
>
> Key: FLINK-13646
> URL: https://issues.apache.org/jira/browse/FLINK-13646
> Project: Flink
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 2.0.0
> Reporter: wangxiyuan
> Priority: Major
>
> OpenLab CI github-app now is added to Flink repo. It's a good time to add the
> related ARM job definition scripts now.
> OpenLab uses zuul[1] as the CI infrastructure which uses ansible[2] for job
> execution and definition.
> The ansible scripts for job definition is always contained in a file named
> *.zuul.yaml*. Here is an example[3].
> So for Flink ARM support work, I suggest to devide it into some steps(we will
> add *flink-core* and *flink-test* related modules as the beginner. Other
> modules can be added later if people want them):
> # Add the basic *build* script to ensure the CI system and build job works
> as expect. The job should be marked as non-voting first, it means the CI test
> failure won't block Flink PR to be merged.
> # Add the *test* script to run unit/intergration test. At this step the
> *--fn* parameter will be added to *mvn test*. It will run the full test cases
> in Flink, so that we can find what test is failed on ARM.
> # Fix the test failure one by one.
> # Once all the tests are passed, remove the *--fn* parameter and keep watch
> the CI's status for some days. If some bugs raise then, fix them as what we
> usually do for travis-ci.
> # Once the CI is stable enought, remove the non-voting tag, so that the ARM
> CI will be the same as travis-ci, to be one of the gate for Flink PR.
> # Finally, Flink community can announce and release Flink ARM version.
> OpenLab will keep helping and maintaining the ARM work. If you have any
> question or requirement, welcome to job IRC channel: #askopenlab
> Any thought?
> Thanks.
> [1]: [https://zuul-ci.org/docs/zuul/]
> [2]: [https://www.ansible.com/]
> [3]: [https://github.com/theopenlab/flink/pull/1/files]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
