Use fetch-javascript-content-tarball role
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:
parent
5df2bbcfe0
commit
0a9e4e59ee
|
@ -1,5 +1,5 @@
|
|||
- hosts: all
|
||||
roles:
|
||||
- fetch-javascript-output
|
||||
- fetch-javascript-tarball
|
||||
- fetch-javascript-content-tarball
|
||||
|
||||
|
|
|
@ -842,7 +842,11 @@
|
|||
name: publish-openstack-javascript-content
|
||||
parent: publish-openstack-artifacts
|
||||
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
|
||||
run: playbooks/javascript/content.yaml
|
||||
post-run: playbooks/javascript/publish.yaml
|
||||
|
|
Loading…
Reference in New Issue