[
https://issues.apache.org/jira/browse/STORM-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188954#comment-17188954
]
liusheng commented on STORM-3401:
---------------------------------
Hi,
Until now, we have enabled 1 basic ARM CI job in Storm upstream which run the
"Client" module of Storm tests on the Travis ARM infrastructures, see
https://issues.apache.org/jira/browse/STORM-3681 But unfortunately, there are
still some block issues of Travis ARM support itself, and seems now there isn't
reponse from the Travis communityabo, please see:
[https://travis-ci.community/t/output-is-truncated-heavily-in-arm64-when-a-command-hangs/7630/|https://travis-ci.community/t/output-is-truncated-heavily-in-arm64-when-a-command-hangs/7630/5]
[https://travis-ci.community/t/disk-quota-exceeded-on-ppc64le/8006/4]
The above issues cause the Storm ARM CI jobs for other modules(Server, Core,
External, Integration-test) are unstable and easy to fail. see:
[https://github.com/liusheng/storm/pull/10/checks?check_run_id=970345930]
According to previous disscussion and the suggestion from [~srdo], it is not
suitable for Storm community to integrate the OpenLab as a 3rd party external
CI system. But due to above issues of Travis ARM CI itself, maybe we can bring
up a trade-off solution? We can add a *daily periodic* ARM CI job which run all
the Storm test cases of all Storm's modules in OpenLab CI system and sent the
testing results to Storm mailing thread. The CI job in OpenLab will don't
integrate anything with Storm code repo or current Storm Travis CI system, it
will pull the code from Storm repo and run all the building and testing
process in OpenLab's ARM server, only need to be given the permission to sent
the testing results to Storm mailing list. And, if we don't want the CI results
noise flush in Storm Dev mailing list, we can confirgure to sent testing
results in a new specify mail channel only when CI job in Openlab run failed.
There is an existed example of Apache Kudu project, please see:
[https://www.mail-archive.com/[email protected]/msg01324.html]
Hi [~srdo] [~ethanli], Could you please give some suggestion about above
proposal ?
> There is no ARM CI for Storm
> ----------------------------
>
> Key: STORM-3401
> URL: https://issues.apache.org/jira/browse/STORM-3401
> Project: Apache Storm
> Issue Type: Improvement
> Components: build
> Reporter: Yikun Jiang
> Priority: Major
>
> Now the CI of storm (in github) is handled by travis-ci. While the test is
> running under x86 ARCH, the arm ARCH is missing. This leads an problem that
> we don't have a way to test every pull request that if it'll break the storm
> deployment on arm or not.
> We should add a CI system that support ARM ARCH. Using it, storm can
> officially support arm release in the future. Here I'd like to introduce
> OpenLab to the community. [OpenLab|https://openlabtesting.org/] is a open
> source CI system that can test any open source software on either x86 or arm
> ARCH, it's mainly used by github projects. Now some
> [projects|https://github.com/theopenlab/openlab-zuul-jobs/blob/master/zuul.d/jobs.yaml]
> has integrated it already. Such as containerd (a graduated CNCF project, the
> arm build will be triggerd in every PR,
> [https://github.com/containerd/containerd/pulls]), terraform and so on.
> OpenLab uses the open source CI software [Zuul
> |https://github.com/openstack-infra/zuul] for CI system. Zuul is used by
> OpenStack community as well. integrating with OpneLab is quite easy using its
> github app. All config info is open source as well.
> If apache storm community has interested with it, I can help for the
> integration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
