The publish-openstack-python-branch-tarball job run by many projects
uses tox (in python-branch-tarball/post.yaml), so needs it installed.
Change-Id: Iba219ad14523ce900d9562ef56c78cc6c15aa01d
Pip is used by this task, make sure ensure-pip is used so it is
present.
While here, install git-review to a venv and symlink it globally to
keep things separate.
Change-Id: If6b1abd2545c68f727bddc5317797236f451b67c
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Signed-off-by: Ian Wienand <iwienand@redhat.com>
We ended up not creating centos7 arm64 wheels and don't have this
volume, don't try and release it.
Change-Id: Ibe4d459ce6c9c6e26330944f30272925b930ba3d
We were installing git-review under python2 in order to propose updates
to Gerrit. git-review happily runs under python3 so update the
installation to avoid python2.
Change-Id: I1671345d71cd60f6508a2c067c4e308680234afe
With change I15d451f6a832b2e698b28e7351a36ef7aea92abe
generate-constraints needs python 3, setup the venv using python 3.
Change-Id: I3dba35267dc6f344ad27910c7dc18c1a33abf4ba
We can not speculatively test changes to the wheel build jobs while it
is project config. These jobs are in the gate for the requirements
project, which run them when bindep.txt changes.
https://review.opendev.org/731394 moved the build-wheel-mirror-base
job/playbook/role into openstack-zuul-jobs, renamed as
build-wheel-cache-* to a) distinguish the name and b) make it a little
clearer that we're building the wheels that goes on the mirror, rather
than passing through to mirroring something existing.
This updates the job names in project-config to reference these new
jobs.
Note the publishing steps are kept here along with the AFS secret.
Depends-On: https://review.opendev.org/732085
Depends-On: https://review.opendev.org/732087
Depends-On: https://review.opendev.org/732083
Depends-On: https://review.opendev.org/732084
Depends-On: https://review.opendev.org/732086
Change-Id: Iac3a906803177e8365f4cfb611800b5ccaed4a6e
To use the write-root-marker role from opendev/base-jobs, set
the root_marker_dir to the same value that is currently set
by the openstack-zuul-jobs role.
Needed-By: https://review.opendev.org/731460
Change-Id: I169f069aa458bc7d02f9c0295702c1316fff825f
Fix:
rsync: mkdir "/src/yaml2ical/calendars" failed: No such file or directory (2)
It's /srv, not /src as a few lines above.
Change-Id: I86326fa7de68a0db7e6893e8ab291ba33fe6018d
The periodic job fails, example:
https://zuul.opendev.org/t/openstack/build/85f380fb6dde462e85a09bc9b5105ba9/
error is:
rsync: change_dir "/home/zuul//src/opendev.org/openstack/project-config/output" failed: No such file or directory (2)
Problem is that the output directory is in the irc-meetings directory
instead.
Use correct path.
Change-Id: I8e15cbfc9a0c01066de68730709c8c30b234c5f5
We're currently adding the private key of a jenkins user. But we
don't use jenkins, so this is lame. Use the zuul deploy key for
project-config instead.
This needs to run as project-config so that per-project deploy
keys work. To do that, shift it from being triggered by irc-meetings
to being triggered hourly by project-config.
As a followup, we should probably convert this to just publish to
AFS and serve the content from there.
Depends-On: https://review.opendev.org/721098
Change-Id: I7874ef46a616e8fd68cf8d95afc3928d3440ba51
after requirements branches we will remove py27 and py37
Change-Id: I5fde605634108dd628df546a2318731e1832b6b3
Signed-off-by: Matthew Thode <mthode@mthode.org>
The install- roles have been renamed to ensure-*, follow the rename.
Depends-On: https://review.opendev.org/716698/
Change-Id: I2522028e9091efdbe292529474de7cce2cf29039
- Use zuul_return fake module to make ansible lint happy, this allows
to remove Zuul import.
- While ansible-lint 4.2.0 is now able to detect playbooks/roles, this
is broken, so don't use it
- move its config out of tox.ini so it can be used by any tools, or
without tox
Change-Id: Ie8935f47db855647e19ae091044e5ac1871f1551
Co-Authored-By: Sorin Sbarnea <ssbarnea@redhat.com>
Co-Authored-By: Andreas Jaeger <aj@suse.com>
There are at least two problems here. The first is we can't create an
afs token because we don't have access to the afs secret. The old ssh
based secret was removed by:
https://review.opendev.org/#/c/706734/2/zuul.d/jobs.yaml
Fix that by adding the new opendev tarballs secret to the job.
Next we need to prefix translation sources with translation-source/ in
the filesystem path. This requires us to write out to a different afs
path than normal. To address that we add a new playbook that is aware of
this different path.
Change-Id: I8b49e4d91600377c98e003b806a13fc89d2614ec
I believe this is now replaced by the base-minimal job from
opendev/base-jobs [1]. This hasn't been updated to upload logs to
swift, so it hasn't been used in quite some time.
[1] 9b235be0c0/zuul.d/jobs.yaml (L96)
Story: #2006598
Task: #37735
Change-Id: I097142dba378b7913e796d06c5a393d86e9e0bbf
playbooks/publish/service-types.yaml is not used anymore, with AFS
publishing it got obsoleted and can now be removed.
site_specs and site_specs_promote are not used anymore, remove them.
Change-Id: I0c3ca2455b4f8b721d48d44780dbc397ddc9cb20
The new job publish-openstack-stackviz-element is working now,
move the trigger in-tree and change the publish location, we do not need
the "-new" in the name anymore.
Content is published at:
https://tarballs.opendev.org/openstack/stackviz/dist/
The tarballs are equal, only difference is filenames of sources.
Mark the job to run only on master, since it publishes always to the
same location and each invocation overrides the file. This is a
safety measure.
Depends-On: https://review.opendev.org/710754
Change-Id: If9488d7c60b58f51a7a0a4bdf0740d16f61c241e
The stackviz publish job fails with
"The task includes an option with an undefined variable. The error was:
'zuul_work_dir' is undefined"
Use zuul.project.src.dir instead of zuul_work_dir.
Change-Id: I443d0b4bfb30a06d68321d402802ae1b433bab6b
The fetch-javascript-output does not work with the artifact uploading,
it does not create an artifact directory on the server.
Remove use of the role and instead copy the needed bits of
fetch-javascript-content-tarball into the playbook.
Change-Id: I3ed46c1acf023b6d2b323f56ce6bdfe07f70775f
We cannot change the javascript-content job as desired, use
specific post job to rename and fetch the tarball.
Change-Id: I63872db707bd674ebfaa9bd49a1cdf3ae6906a60
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 job only publishes part of the directory and needs to keep old content
around. Thus, add a new promote playbook that uses the
upload-afs-synchronize rule to not delete old content like the normal
playbook in the parent does.
Change-Id: I13f9faf698ec459f1d7cd7a950172d836b470a4c
Remove publish-tox-docs-static, the last user has been converted to AFS
publishing.
Remove the parent base-publish-tox-docs-static as well, it's not used
anymore.
Remove playbook files and secrets used by these jobs.
Depends-On: https://review.opendev.org/708918
Change-Id: I68b3ab7e597e230617ec1eaa8217d4f5f4c5fb15
Add new job publish-tox-docs-releases for publishing of releases repo to
new AFS location to obsolete static.o.o publishing.
Task: #37724
Story: #2006598
Needed-By: https://review.opendev.org/708918
Change-Id: I804f6ddb0b10b4aa3fac6a3cf11a2d23b8b4e730
Following-on from Ia3a0358249e9ed3d766b1b61535f2f6d67d4eb2d, this
removes the publishing from the static site, which is now happening to
AFS.
The site_tarballs secret is no longer required. The two jobs still
using it have a parent of publish-openstack-artifacts so should not
need a separate secret.
Depends-On: https://review.opendev.org/706732
Change-Id: I1b1db7d2451d7fb1fdd7921e7c9efd0e020fbce6