[Demo][DNM] Add OpenLab CI configuration for ARM64 build

[Yikun]

This patch adds the CI configuration to enable the support for arm
build in OpenLab.

After this, each pull request in theopenlab/storm will trigger the
storm-arm64-build job which verified the arm build on ARM cluster.

[Yikun]

recheck

[Yikun]

You can see the job is running in openlab [1]:

Once the job is completed, the OpenLab robot will give a comment in here to tell us the results and job log link.

[1] http://status.openlabtesting.org/status

[srdo]

@Yikun Looks great. What happens if the build fails on OpenLab? Is there some way to access the files from the build, or publish log files on error?

I'm asking because this has been an annoyance on Travis, where if the build fails we don't publish the log files, so it's hard to tell exactly what broke.

Edit:
By log files I'm referring to the test logs in target/surefire-reports in each module.

[theopenlab-ci]

Build succeeded.

• storm-build-arm64 : SUCCESS in 53m 37s

[srdo]

Also is there any cap on how long builds are allowed to run on OpenLab? We split the Travis build into modules to ensure that we don't hit the one hour cap on builds there.

[theopenlab-ci]

Build failed.

• storm-build-arm64 : FAILURE in 3m 05s

[Yikun]

What happens if the build fails on OpenLab? Is there some way to access the files from the build, or publish log files on error?
I'm asking because this has been an annoyance on Travis, where if the build fails we don't publish the log files, so it's hard to tell exactly what broke.

^ I add a commit to let the job down. : ) we will see what the failed job looks like. The openlab will collect all log files of build script.

But for the project test logs, we provide the mechnism to archive the logs and testresult.

A typical directory structure looks like:

The logs is somewhere to collect the key log files($LOGS_PATH), and the test_results($RESULTS_PATH) is somewhere to collect the meta or some other archive files. So, if the storm need to collect specific file we could put it into $LOGS_PATH or $RESULTS_PATH

Also is there any cap on how long builds are allowed to run on OpenLab? We split the Travis build into modules to ensure that we don't hit the one hour cap on builds there.

The default timeout is 10800 sec (3 hours)，we can adjust it for each job in job defination.

[theopenlab-ci]

Build failed.

• storm-build-arm64 : TIMED_OUT in 3h 00m 39s

[theopenlab-ci]

Build failed.

• storm-build-arm64 : FAILURE in 12m 18s

[theopenlab-ci]

Build succeeded.

• storm-build-arm64 : SUCCESS in 47m 32s

[theopenlab-ci]

recheck

[theopenlab-ci]

Build succeeded.

• storm-build-arm64 : SUCCESS in 45m 35s

[Yikun]

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y nodejs

[theopenlab-ci]

Build succeeded.

• storm-build-arm64 : SUCCESS in 47m 38s