[Azure Dev Ops][armel] Enable armel/Tizen jobs in Azure Dev Ops

[jashook]

Change the tizen(armel) jobs to run using helix. This will unblock moving the armel jobs from netci to azure dev ops. Currently there are several things that blocking this effort, see the summary below.

1. A reproducible dockerfile to create the tizen image we use in netci checked into https://github.com/dotnet/dotnet-buildtools-prereqs-docker.
   • Current docker image used is: tizendotnet/dotnet-buildtools-prereqs:ubuntu-16.04-cross-e435274-20180426002255-tizen-rootfs-5.0m1
   • The image that will be used in https://github.com/dotnet/dotnet-buildtools-prereqs-docker should be able to build armel, and also should be able to chroot into the rootfs to run the built coreclr
2. Arm32 hardware (either raspberry pi or jetson tx2) in the lab in its own helix queue, which can run docker.

---

The proposed testing plan is:

1. docker run -i --rm -v coreclr:/coreclr -w /coreclr -e ROOTFS_DIR=/crossrootfs/armel microsoft/dotnet-buildtools-prereqs:ubuntu-16.04-cross-armel ./build.sh armel cross checked

2. docker run -i --rm -v coreclr:/coreclr -w /coreclr -e ROOTFS_DIR=/crossrootfs/armel microsoft/dotnet-buildtools-prereqs:ubuntu-16.04-cross-armel ./build-test.sh armel checked

3. helixpublishwitharcade.proj

---

Helix nodes will run on arm64/armhf hardware, connected under the tizen docker image. Once helix supports running under docker, we can change this to point at the new tizen image.

[jashook]

/cc @RussKeldorph @sbomer @safern

[jashook]

/cc @BruceForstall

[jashook]

/cc @dotnet/arm32-contrib

[alpencolt]

cc @gbalykov

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[ghost]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.