tree 56cceb5a015b7e3d00f3c144742ed0f0b7411685
parent 354353bc3e89818512c14aca5f73b8613b796b67
author Jan Kundrát <jan.kundrat@cesnet.cz> 1559769938 +0200
committer Jan Kundrát <jan.kundrat@cesnet.cz> 1559770832 +0200

Uploading artifacts to Swift

There's a new role, the `upload-artifacts-swift`. It is a pretty
bare-bones role which should serve as a (mostly) drop-in replacement of
the add-fileserver + publish-artifacts-to-fileserver combo. It still
requires "something" to ensure that the artifacts are available at the
executor, and it will not register these artifacts, nor return them to
Zuul. That all should be done separately (check the rest of our CI setup
for details, especially publish-artifacts-base and
publish-artifacts-tenant in ci/project-config.git), this one is only a
building block.

The rest happens in the updated role `download-artifacts-from-check`. It
is no longer intended to run within the post playbook; it should now be
defined in a parent job's `run`.

Also, I'm moving everything to the executor so that we don't require a
dummy build node. This necessitated a fix to the executor's bubblewrap
configuration for accessing the TLS certificates and preferences and
what not.

Change-Id: I4e4bb26e5976127ca8c504ed3e6d1f8b9ede9393