Jun He,
I just modified two CI jobs[1][2] you created but then I realized I should
discuss with you first before the modification. So, I'm sorry in advance.
What I'd like to discuss is I saw your way to setup these CI jobs is to
have a matrix of supported distro + arch * build slaves. The matrix looks
like this:
slave01 slave02 slave-aarch-01
slave-ppc64le-01
distro + arch 1 O O X
O
distro + arch 2 O X O
O
This may have slaves running same arch producing duplicate images. See
below example:
* slave06:
bigtop/puppet 1.3.0-ubuntu-16.04 6527358ce96e 3 days ago
318MB
* slave07:
bigtop/puppet 1.3.0-ubuntu-16.04 29f1b8969d31 2 days ago
318MB
This may have problem since we can't trace the lineage of downstream
images. For example, the bigtop/puppet image pushed to dockerhub is
6527358ce96e, but bigtop/slaves image pushed to dockerhub may be based on
29f1b8969d31(though I didn't check). Hence we need a stable foundation to
evaluate the bigtop software stack.
I've [1] and [2] modified to build images on whatever slave that is capable
of building it. Once images are built, we can trigger pull job to sync all
the images back to all slaves. Do you think this makes sense? Would love to
hear your feedback. And thanks for your hard work!
Best,
Evans
[1] https://ci.bigtop.apache.org/view/Docker/job/Docker-Puppet-1.3/
[2] https://ci.bigtop.apache.org/view/Docker/job/Docker-Toolchain-1.3.0/
