The install- roles have been renamed to ensure-*, follow the rename.
Depends-On: https://review.opendev.org/716698/
Change-Id: I2522028e9091efdbe292529474de7cce2cf29039
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
Turns out playbooks/javascript/publish.yaml is also used in
generating branch tarballs, which we don't want to sign. This has
resulted in the publish-openstack-javascript-content job, e.g. for
the openstack-infra/storyboard-webclient project which runs it after
every commit, to fail with:
The task includes an option with an undefined variable. The error
was: 'gpg_key' is undefined
We probably need to switch to running separate versions of this job
for tags and branch updates so that we can exclusively sign the
former.
This reverts commit 7244f69975311ac8f570082e419d45563ca7cc16.
Change-Id: I77fd1bd315d96f8fe082b3e50a430cd8602c4d71
There is a substantive difference between a content tarball and a source
tarball that was getting missed. Update the docs to indicate what a
'content' tarball is, and then update the
publish-openstack-javascript-content job to use the
fetch-javascript-content-tarball role.
Change-Id: I055ed8248f8243926601c0445ab7c911054fdeb0
Depends-On: https://review.openstack.org/550223
The `version-from-git` role doesn't serve a purpose in this playbook,
and seems to cause issues when there are no tags in the project's
repository to get the version from.
Change-Id: I04ed1e172eb795843c9ef58b97611edb4ebb41aa
The publish-openstack-javascript-content job specifies
`playbooks/javascript/publish.yaml` as a post-run playbook,
but this playbook doesn't exist. This commit adds this
missing playbook, which fetches the javascript output and
tarball for publishing to tarballs.o.o.
Change-Id: I6c0ad5e2e0d35f3d331e4dd18edca79a4649b79a
We were only fetching the tarballs on the release jobs, not on the
publish jobs. That makes the publish job not so much of a publish job.
Change-Id: I8e6b12e61bcc42d2896c4fb574aaf6f1718e1bdb
All of these invocations of the bindep role are passing what amount to
the defaults. In zuul-jobs, doing bindep_dir: "{{ zuul_work_dir }}" is
important because it allows in-repo uses of those jobs to override how
they work for things like triggering from one repo but running on
another.
The publication jobs in project-config do not need that level of
flexibility, so just remove params and let defaults take over.
As a follow up, we could also add defaults for zuul_work_dir - and
honestly for bindep_dir - to the base job. That way we can always count
on them being set to a sane default value, and they're still
overrideable in a job.
Change-Id: I5bcda84aefa4726d0a904e8bc9698c21ca07f9a5
There are two different types of tarballs we want to publish, a source
tarball to npm, and a built tarball intended for deployment. We have a
job for dealing with tarballs to npm, but we're lacking a new-style job
for publishing built artifacts to tarballs.o.o.
Add one, and switch storyboard to using it.
Change-Id: I19607d14facb93d1f46ea68feba563badfbbb5a2
Ansible set_fact sets variables into the hostvars of the host they are
running on. We need to consume the remote hostvar for package_ver in the
context of localhost. So reach in to hostvars.
Set the host to ubuntu-xenial rather than all to be explicit.
Change-Id: I5a5c593cdf80d721a36187e1c552db21f4794b37
The upload-npm role seems to expect to upload files from the
executor, so in the javascript post playbook we should tell it to
run on localhost rather than the job node.
Change-Id: Iee176655108362545029f87134e9f150e0e35c17
The current legacy javascript publish jobs are super broken. This adds
one that will use the roles from zuul-jobs and then will publish the
contents to npm.
Depends-On: I7f7c031ce754838776043325025fe5928cd36135
Change-Id: Ib361ee2880be77eff3ef905726b032777d0b807a