This should be a production no-op; it splits the key and source setup
into a separate playbooks, but imports them both in pre.yaml in the
same order.
Currently this job sets up the executor so that it can log into bridge
to run the playbooks, then clones the system-config state into
/home/zuul/src/opendev.org/opendev/system-config on bridge.
This presents a problem for parallel operation; every production job
will overwrite each other's system-config checkout. This is
unnecessary since they are all working in the context of the same
buildset -- we only need to populate system-config on bridge once at
the start and all deployment jobs can share that checkout.
Thus we add two extra jobs to split up the operation of the existing
opendev-infra-prod-base job.
opendev-infra-prod-setup-src sets up the keys so the executor can log
into bridge and also replicates the state of system-config onto
bridge for this buildset. This is intended to run once per buildset.
opendev-infra-prod-setup-keys just sets up the keys so that the
executor can run production playbooks. It is intended that
opendev-infra-prod-setup-src will have already run to put the
correct changeset of system-config on bridge.o.o. This way,
production jobs can run in parallel all using the same copy of the
source without overwriting it.
These are used in https://review.opendev.org/c/opendev/system-config/+/807808
(This will eventually leave opendev-infra-prod-base unused, it can be
cleaned up in a follow-on)
Change-Id: I1bbf4f1402938216401dd924da62aa869a08875b
aa42212e7e