Arvados

I've been exploring Jenkins a bit, and this is what I found:

• The arvados-cwl-conformance-tests pipelines failed because the arvbox-demo docker image wasn't available.
• The arvbox-demo docker image is created and uploaded by the docker-arvbox pipeline, that runs as part of the run-tests pipeline.
• The arvados-cwl-conformance-tests pipelines are run from the docker-jobs-image pipeline, that is launched from build-packages-multijob, that is launched from build-packages-python-ruby, that is a sibling pipeline of docker-arvbox.

What I think is happening here is that sometimes the docker-arvbox pipeline doesn't finish before the arvados-cwl-conformance-tests jobs run. One supporting fact of this hypothesis is that retrying the arvados-cwl-conformance-tests job was able to get the arvbox docker image without issues.

We might need to revisit the Jenkins jobs' interdependencies to make sure the arvbox docker image is available by the time the rest of the jobs that need it, start running.

The failure at arvados-cwl-conformance-tests: #1305 /label=federation,pythoncmd=python3,suite=integration/console seems to not be related to a missing docker image but something else.