As a first step towards supporting multiple ansible versions we need
tooling to manage ansible installations. This moves the installation
of ansible from the requirements.txt into zuul. This is called as a
setup hook to install the ansible versions into
<prefix>/lib/zuul/ansible. Further this tooling abstracts knowledge
that the executor must know in order to actually run the correct
version of ansible.
The actual usage of multiple ansible versions will be done in
follow-ups.
For better maintainability the ansible plugins live in
zuul/ansible/base where plugins can be kept in different versions if
necessary. For each supported ansible version there is a specific
folder that symlinks the according plugins.
Change-Id: I5ce1385245c76818777aa34230786a9dbaf723e5
Depends-On: https://review.openstack.org/623927
Rpm %install step skip those directory when those files are missing.
Otherwise those directories need to be added as package data.
Change-Id: Ied017ab576d67559cd2c19e4c37c1f3e4ec5183f
Behavior changes between v2 environment variables and the v3
zuul_legavy_vars filter may cause regressions in some translated
jobs, so be very explicit about which variables were intentionally
omitted, which variables are completely new, and which variables are
now appearing in pipelines they did not previously.
Change-Id: Idf032f9903b21e383a733ab9ff1a6ec80f636e4a
We need the last 2 digits from the change number to define XX in
refs/changes/XX/512270/2. Currently, we get everything but those
last two digits.
Change-Id: I84ebe2d048574e07e3eb838379c10854d775f131
Jobs that need this expect it as an environment variable.
Update the migration script in case it gets used again.
Change-Id: Ic4d372a795e17a33116d19e9e4603fb5a08fe152
Tobias Henkel