This performs the final infra cleanup for the x/devstack-plugin-bdd repo
to complete its retirement.
Change-Id: Iec6316ebfa402237624deaf5dd1f82ce6578ecf6
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
We do not uplload from opendev to puppet forge anymore:
Remove usage of puppet-forge uploads jobs from opendev. This removes
the useage of release jobs:
- legacy-puppet-storyboard-forge-upload from puppet-storyboard
- legacy-puppet-httpd-forge-upload from puppet-httpd
Change-Id: Id6e2ddcc3cbced430f73efdf03b6425cf043209a
stackviz gets published daily to:
https://tarballs.opendev.org/openstack/stackviz/dist/stackviz-latest.tar.gz
The current job periodic-package-stackviz-element is a legacy job,
create a new job publish-openstack-javascript-latest-content that can be
run instead.
The stackviz-element is backed into our images and thus we have to be
extra careful not to break it and test.
The new job is publishing temporarily under a different filename to
check that it's working correctly.
Order of changes:
* Merge this change, so we run both periodic-package-stackviz-element and
publish-openstack-javascript-latest-content in stackviz.
* Change new job to publish under correct name and remove setup in
project-config.
* Switch to new job in stackviz repo.
Change-Id: I81ac0975f03756da673ae12e7e11cd5686a0f2d6
This is step 2 in the retirement process for the x/devstack-plugin-bdd
repo.
Change-Id: Ia7b04565c26d1c37ee0c6b44a505af4e29656b99
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This deliverable was added under ironic project
governance, with a first official release planned
for the Ussuri cycle.
Change-Id: I14deed42f03c37461d337bb1192de770d15ab6cf
The python2-based jobs from integrated-gate are failing now since
Neutron requires py>=3.6. So drop that template from the devstack-gate
project.
The alternative would be to run those jobs against a stable branch
instead master, but that would be non-trivial since devstack-gate is
branchless.
Also the expected remaining lifetime of ds-gate is limited, since it is
a current community goal to convert all legacy jobs to new versions,
which will obsolete the devstack-gate code. With that argument I also
refrain from moving the whole job setup into the project itself, as we
would do with any project that still has a future.
Change-Id: If094fcc31929193eb8278bdbb182e24aa506cca7
Removing coreos-image-builder as it was never
really put into use.
As such, we're moving to retire it.
Please see: https://review.opendev.org/#/c/707181/
Change-Id: I50574d142e246e3256d90c6d0aa7295655e05d43
As part of dropping py27 support, openstack-python3-ussuri-jobs
has been added to networking-vpp's .zuul.yaml file:
https://review.opendev.org/#/c/705394/
Hence, removing the networking-vpp entry in zuul.d/projects.yaml
as it is no longer needed anymore.
Change-Id: I0d9c01324202270da9826d5490609288b11901ad
This adds publishing of artifacts to AFS in parallel with the existing
publishing to the static volume.
The additional tasks added to the openstack-artifacts.yaml playbook
have been tested in the project-config-test-artifacts-to-afs test
(results at [1]) and also in an external project
ironic-python-agent-builder (see notes in [2]). Thus we can have high
confidence it will work.
After this merges, I will manually rsync the old static tarballs data
to the AFS directory (again; it has been sync'd previously) and from
that point on both should be exactly the same.
At that point we can switch the DNS entries for
static.<openstack|opendev>.org (the sites have been created with [3])
to the new server and we will be fully migrated to the AFS volume. We
can then remove the static publishing.
[1] http://files.openstack.org/project/tarballs.opendev.org/openstack/project-config/afs-copy-test/
[2] https://review.opendev.org/705161
[3] https://review.opendev.org/704913
Change-Id: Ia3a0358249e9ed3d766b1b61535f2f6d67d4eb2d
Python 2.7 support and tests were already dropped from networking-spp.
And openstack-python-jobs-neutron job contains openstack-tox-py27 job.
So this patch removes openstack-python-jobs-neutron job from
networking-spp.
Other tests contained in openstack-python-jobs-neutron are contained
in jobs which specified in networking-spp's zuul.yaml.
And, this patch also removes check-requirements job from
networking-spp.
check-requirements job is specified in networking-spp's zuul.yaml.
Change-Id: Idfc286489bdc9d89e2bae9316e31607fca244a54
This is part of our efforts to get tarball publishing onto AFS volumes
[1].
Test a new artifact publishing job that puts output at
/afs/.openstack.org/project/tarballs.opendev.org. This is intended to
replace the existing publishing job when it is working.
[1] https://docs.opendev.org/opendev/infra-specs/latest/specs/retire-static.html
Change-Id: Ied96194e1904fee232e144a4e89ec8ba2252e42e
We publish now to AFS and have no need to duplicate publishing anymore,
remove temporary jobs.
Note that the uc jobs were switched, we keep the AFS one.
Change-Id: Ifc2f8b0023456aa1a27c74bcdf32a93ef9b8f03f
Transparency-policy repo is dead and the content lives on
www.openstack.org, remove the publishing. We can add it back if the repo
gets active again and publishes elsewhere.
Change-Id: I774cf28fe93e7b0337368e32884c3d7a2477ae54
Remove trusty wheel jobs in preparation for node removal. No jobs
should be using the wheels any more.
Depends-On: https://review.opendev.org/702773
Change-Id: I9b272782c83cff4e456958be2eb3a38ec60aca6a
The dependent change introduces a non-trusty based job, switch to that
Depends-On: https://review.opendev.org/702768
Change-Id: If4fd66c4c08e8b8de1877d1fbcfc6bb2b3d7dea3
This repo is not used anymore, it's been forked and taken over.
Remove jobs and add noop-jobs so that we can remove jobs and retire repo
if needed.
Change-Id: I67e67a1e98d85e5a8ed31001b26e280e29bc6318
We're dropping Python 2.7 support, so the "openstack-python-jobs"
template should also be removed.
While at it, we'll move all templates within the project, except for
"publish-to-pypi", which is expected to stay here.
Change-Id: I8b61bdaf9a6f253dfa13fb7dd1689440a79f517a
Let cloudbase-init's .zuul.yml define the zuul gates.
The publish-to-pypi template can be left as-is, so that
the pypi package gets updated on new tags/releases.
Change-Id: Ia23ee2e1a769d17c6c486bcf4d192897e98e086a
Legacy jobs are failing and block gating.
The other jobs are using legacy nodejs which is not
of interest either.
The plan is to move all job definitions into the
deliverable repository and port them to Zuul v3 format
and current nodejs (10, 12).
Depends-on: https://review.opendev.org/701854
Change-Id: I34cf69ee118010aa62a4bd3c601b6038a871bfea
Sean McGinnis