We have some headroom on the logs filesystem and this allows us to go
back to more reliable methods of grabbing logs. Specifically we are not
required to have http access back to the jenkins master from every job
that runs into order to get the console logs then upload them to swift.
Change-Id: Ie8479c224b2fd3c3efca4e1bf4157656540eccff
Ensure that the release notes job that runs after a patch merges or when
a tag is applied always checks out the master branch of the project so
the full set of notes is built, and not just the version from the branch
into which the patch merged.
Change-Id: I7cbb0f60d8120300c438cb44598b9f7b16e8abe5
Closes-Bug: #1552911
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
No projects uses the constraints jobs anymore, we can remove the jobs
from Jenkins setup now.
Remove also conditions for constraints in zuul/layout.yaml that are not
needed anymore since there's no job called -constraints anymore.
Change-Id: I93f2fc2a875ceab9483e9170274761e82d497aed
Depends-On: I48ecd961d68b36e5d418171cc449681092816523
Projects using openstack-server-publish-jobs publish documents both from
post and release pipelines. Now a tag on stable branch will publish the
documents both to developer/$project/$tag and developer/$project. This
overrides the documents published in the post pipeline - replacing
master documents with stable documents.
The publishing to both locations is correct for projects that only
publish as part of releases but not for those useing
openstack-server-publish-jobs.
To fix this:
Create a new job '{name}-docs-tags-only' that adds a new parameter to
run-docs script. If that parameter is passed, tag publishing will only
happen to developer/$project/$tag . Add the new job to the
openstack-publish-jobs so that all projects can use it.
Adapt openstack-server-publish-jobs in zuul to use the new job.
This change also adds constraint version of the publishing job. A new
builder docs-tags-only-env has beend added for the new jobs.
Change-Id: If0d000358f17a7d9ea0b8c3e3aada1c16291b3ee
Use branch-git-prep instead of zuul-git-branch-prep to prepare the local
source repository, since it appears the latter does not work properly in
post jobs, yet.
Change-Id: I8cbcd49ff4bf7234e149985535f394bb686c58c3
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Between the Icehouse and Juno releases, OpenStack changed its
supported Ubuntu LTS platform from Precise to Trusty. In support of
continuing testing stable/icehouse and prior branches on Precise
while starting to test newer branches on Trusty, a branch-based
decision tree was introduced into our Zuul configuration by way of
complex parameter functions with an ever growing list of regular
expression matches on job names.
Now that Icehouse is EOL (in fact, Juno is too) this simply adds
unnecessary complexity and an attractive nuisance for cargo-cult
copying into new job and job-template definitions which don't even
need it. In preparation to remove the associated parameter
functions, get rid of multiple labels in all jobs and set them to
whatever label Zuul would ultimately select.
This change touches a vast number, possibly a majority, of our jobs
and so manual jenkins-jobs updates on all Jenkins masters will be
needed after this merges, before it's safe to approve the
corresponding Zuul configuration cleanup.
Change-Id: Ic952ee02da2c77fe2ace81c4e2fa87531be6119c
Use zuul-git-branch-prep macro, the branch-git-prep does not work in the
post queue (gerrit-git-prep script still gets ZUUL_BRANCH and checks out
a stable branch instead of desired master) to check out master as
intented.
Using zuul-git-branch-prep we can now for any change publish the release
notes from *master*.
This fixes also zuul-git-branch-prep, we need to properly quote the
function.
Also, only run the job on liberty and newer branches - incl. master - since
older branches do not have reno based releasenotes entries.
Change-Id: Icce6440278c6606528f8f601da76b2af0a1f12e9
This flips master and stable/liberty to use -constraints unit tests as
voting. The unconstrained jobs are dropped from master and liberty.
Implements Blueprint: Requirements-Management
Change-Id: I152ed78813e46ffc3f72ff7dec5ed2872268f5bd
Upload the generated draft releasenotes so that they can be easily
reviewed - similar to documents with just clicking on the gate.
Rename the job to gate-{name}-releasenotes, the tox is not needed
anymore in the name.
Change-Id: Ib542084a275a5bfe82c48517d48372fec6411e16
Enhance releasenote handling and add a post job that publishes the
release notes.
Note that the post jobs will be run on all branches but we need
to publish the content from master since we generate all content
on the master branch.
Add job to post queue for publishing release-notes.
Change-Id: I204e669d532d59bbf6aec0d8d4da4ab183deaf59
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3