This is the first commit in a series to retire the Packaging
Deb project. Step 1 is to end project gating (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
There are some lingering remnants in
jenkins/jobs/packaging-mirror.yml, a publisher 'deb-pkgs'
jenkins/jobs/macros.yml, and noop-jobs in zuul/layout.yml,
which I left for the Step 3 commit to entirely remove the
project from OpenStack Infra.
Change-Id: I53b200dd63b704cbf6f75225d8f8aca8d4fbcbe0
We do not need gerrit-git-prep anymore, zuul-git-prep works on all our
slaves and has the advantage of using zuul-cloner so that the local
cache is used and Depends-On works.
Remove gerrit-git-prep and use zuul-git-prep instead everywhere.
Change-Id: I2f106af58f78fceaf3c497fe43e6f5a002695645
Paul wrote a Debian repository publisher post job, but it's using
deb-openstack-pkg-tools instead of openstack-pkg-tools as the
path from where to pick-up the package. Therefore, the files should
be pushed to /packaging-deb/deb-openstack-pkg-tools (ie: with deb-
in front) for it to work. Hopefully, this will be the last fix
of upload path.
Change-Id: I658ce15d737e10658fcbddba0188d83b838994c1
Previously, we attempted to use tarballs/{project}/ for the upload
of built packages after a merge, but {project} wasn't expanded.
This patch fixes that by adding project: openstack-pkg-tools in
the pkgdeb-publish-openstack-pkg-tools job definition indented
immediately below the "publisher: deb-pkgs" line.
Change-Id: I526977199a68212fe7fc7e5d1d0325af6558a8e9
This is related to zuulv25, we make sure console-log is the last
publisher to ensure zuul-launcher logs are also uploaded.
Change-Id: I1616b97fad2b97fb9e977ec14543aab4bc673b58
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This patch fixes 2 things:
1/ The publish job didn't work, as it missed the double *
2/ Only publish after merge (ie: a post: job) and not on
every patch iteration
Change-Id: I6465056ff737b1fc5606f4f92a2a4e8acd89250d
This patch adds an scp of the content of the uploads folder,
created after packages are built.
Change-Id: I0c3a930480a6496017ef32a85c5bec05679d9018
Depends-On: I477d169f2d2d567344e227659f54b962a68f24e4
Previously, it was attempted to split deb-openstack-pkg-tools.yaml into
2 shell scripts instead of one, to attempt to work around the sbuild
relogin problem. This didn't work, and since, a workaround was found.
Therefore, this patch cleans-up the mess from previous attemp, and
remerges into a single shell script.
Change-Id: Ibfd2dd812d78e2af6afd4a6739a8915214b8fa32
Currently, pkgos-infra-install-sbuild is launch directly after sbuild is
ran. This leads to this error:
"User jenkins is not currently a member of group sbuild, but is in the
system group database You need to log in again to gain sbuild group
privileges"
So this patch splits the single shell script into 2, so that it does
the "log in again" part described in the above error message. This
should fix the problem.
Change-Id: Idf35d7c143e2fb67ccf6cdcefce74c3d45e9a49c
This patch makes it possible for openstack-pkg-tools to build itself.
The normal package build workflow will be to get openstack-pkg-tools
installed with apt-get, then use pkgos-infra-install-sbuild and
pkgos-infra-build-pkg to build.
Though for openstack-pkg-tools, this can't be used, otherwise we have
a circular dependency, and we expose ourselves to the possibility of
having a bad commit on openstack-pkg-tools to break all of the build
system if a bad commit is published as a .deb.
Which is why openstack-pkg-tools must use its own scripts directly.
Once openstack-pkg-tools is reliably built and its resulting .deb
published on an OpenStack infra Debian repository, then a new generic
package build job will be added to project-config.
Change-Id: I7a13b2f298b5426219b6d3842ac1a9cf7a2a3656
Allison Randal