There's no reason to not just build the tarball when we build the
content.
Set the default value for node_version in the base job.
Change-Id: Ifb3e5138e9ae19ec3de9250f1828fc07230ef739
This adds a custom ansible-lint rule at .rules/ZuulJobsNamespaceLoopVar.py
that enforces the loop var policy described at:
https://zuul-ci.org/docs/zuul-jobs/policy.html#ansible-loops-in-roles
It also updates existing roles to follow the policy.
Change-Id: I92b2ff56a1c2702542fc07b316f1809087a4c92f
The recent change to return the artifact URLs for python/js builds
omitted the artifacts/ directory from the URL.
Change-Id: If86749533e73dbfd17317acba22dbd05dff34abb
When producing javascript content tarballs, return artifact records
to Zuul.
Add a new job, build-javascript-content-tarball, which includes the
role to fetch javascript content tarballs.
Change-Id: Ia247054d0523b81916815151fd57138469f634e0
Built content and source tarballs are different. Have a role that
handles uploading built content.
Append -content to the tarball so that a project can publish both a
source tarball and a built content tarball without stepping on each
other.
Change-Id: I33dff8080018bda281a00e648468de80d3ecd679
Sorin Sbarnea