Split the extant job into separate centos7 and centos8 parts (this is
so we can easily just rm the centos7 path when it's not required,
rather than making some mashed up combined job), and add a centos8
job to build openafs packages for centos-8.
This is in preparation for making centos-8 wheels; we copy the wheel
directly from the building host so it needs an openafs client.
Change-Id: I2d6392879aac85431253284f217b9daa4a9af94d
This is currently copying everything into
https://tarballs.openstack.org/project-config/package-afs-centos7/x86_64/
where we don't actually want the "x86_64". Add trailing slash so it
copies the directory contents. Also remove any existing content with
--delete, we only want the latest.
Change-Id: I4b0fe994baaaf04db0fe552f88107d90e328f048
We don't always create afs rpms in our periodic job so we were skipping
the creation of the artifacts dir. Unfortunately the openstack
artifact publishing playbook expects this dir to exist. Fix this by
creating the artifacts dir but not populating it with RPMs if we didn't
build any RPMs for openafs.
Change-Id: I986bca765ae898e9792e789c6852bce1d654d580
The openafs centos packaging job only builds new rpms if the desired
version doesn't have an rpm published. Otherwise it short circuits and
the job ends. Unfortunately the post tasks assume the rpm will always be
built so this job then fails. Fix this by checking for rpms before
running the post tasks.
Change-Id: I132b82d437a19f855a49d175a912792417a85ae9
Rather than tieing this to the migration, just do them.
The afs package build script changed slightly - it now publishes to
tarballs.openstack.org/project-config/package-afs-centos7 instead of
tarballs.openstack.org/package-afs-centos7 so that the normal artifact
publication base job can be used.
The existing package-afs-centos7 has been copied on tarballs.openstack.org to
project-config/package-afs-centos7 so that this will not cause a rebuild.
Change-Id: I7cfb90df4eb49defce7aa41453918347a2c6742e
Ian Wienand