openstack/project-config
Code Issues Proposed changes

Use fetch-javascript-content-tarball role

Browse Source 
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
This commit is contained in:
Monty Taylor
2018-03-06 13:35:25 -06:00
committed by Andreas Jaeger
parent 5df2bbcfe0
commit 0a9e4e59ee
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
playbooks/javascript/publish.yaml
View File

@@ -1,5 +1,5 @@
- hosts: all - hosts: all
roles: roles:
- fetch-javascript-output - fetch-javascript-output
- fetch-javascript-tarball - fetch-javascript-content-tarball

6
zuul.d/jobs.yaml
View File

@@ -842,7 +842,11 @@
name: publish-openstack-javascript-content name: publish-openstack-javascript-content
parent: publish-openstack-artifacts parent: publish-openstack-artifacts
description: | description: |
Publish javascript content tarballs to tarballs.openstack.org Publish javascript content tarballs to tarballs.openstack.org.
Content tarballs contain the built javascript/css/html artifacts. They
are different from source tarballs, which are handled by the
publish-openstack-javascript-tarball job.
pre-run: playbooks/javascript/pre.yaml pre-run: playbooks/javascript/pre.yaml
run: playbooks/javascript/content.yaml run: playbooks/javascript/content.yaml
post-run: playbooks/javascript/publish.yaml post-run: playbooks/javascript/publish.yaml