Sometimes we need to clean the workspaces. While we have a command
documented, go ahead and make a playbook for it.
Change-Id: I1887dec24563811a71157c000b2d8ae9b7850d6a
Change ACLs so that they would apply to proposed/* branches instead of
milestone-proposed branches, and adjust documentation to match.
NB: The top-level project.config should also be changed so that its ACLs
apply to proposed/* branches. It's apparently not driven by the config
repository.
Change-Id: Iad6991315b1d526026e0aeb0e968ed85dd317fac
It turns out that while changes to Gerrit ACLs from the WebUI will
create "Git config" format files which look somewhat like
traditional INI files with hard-tab indentation and other
unpleasantness, Gerrit will interpret more traditional INI files as
ACLs just fine and merge them to refs/meta/config unaltered. Adjust
the examples to look like the sorts of INI files with which our
developers are more familiar, and apply some other helpful
normalization like alphabetizing the section and key orders,
removing redundant default values or other no-ops, et cetera.
Change-Id: I3b9dad7b7beb05427eb4011fa6dad2a6dd4cbe72
Currently there is ambiguity in the third party documentation
around requesting accounts. Some have interpreted the documentation
as stating it is possible to conduct tests using a gerrit user
account. This patch addresses the documentation language making
it clear that a third party ci system is required for third party
ci interactions with gerrit and the system must be created by
infra.
This patch also changes the recommended method of requesting a
third party ci account from three choices (email, bug or irc) to
one choice (email). This edit was previously part of
https://review.openstack.org/#/c/101013/ and has been moved into
this patch.
Change-Id: Iab88b729d714dcaa881376e9237834e877acecfa
Currently the third party ci test artifact retention limit is
one month. This patch adds that information to the docs.
Change-Id: Ice1d13b1d7828eeed9a5856db1d9be649fdfaefe
We need to make sure that jenkins will run jobs on bare-trusty before we
can migrate and projects to bare-trusty. So do the initial JJB prep now,
then we can do a project at a time.
Change-Id: I6e80567730bff8d387d8a5b87d7368ea3be6d3ab
We are making this and other CLA enforcement groups public, since
they are not sensitive information (lists of committers are already
public and we used to keep these tracked in a wiki article before
enforcement within Gerrit), and since there is value in being able
to query this status in a read-only manner to aid in building
contributor analyses.
Change-Id: I459a066612fe014790086ac04cbeb5eebd6e062d
This gets us closer to the behavior we had prior to upgrading from
2.4 to 2.8, and is generally considered desirable since we want
people to be able to review and vote on commit message contents.
Change-Id: I7051a606f1d501e5aef6510d42ef928456d07303
Add page to our CI documenation about the elastic-recheck project
so people can find the full docs and configuration details.
Change-Id: I846d811e5b154c0e555d3458bc74920baf0be971
The nodepool_prod.pp file has a lot of valuable information for
the deployment of nodepool, add this to list of puppet files
in documentation for configuration.
Change-Id: I33401f5b4baa70305b9091bc08e962cb222230ff
The devstack_launch_slave.pp module was removed on 2013-08-18. This
change updates the documentation to reflect that deletion.
Change-Id: I3ae522cfbdc4e3650e4921fb633b21192f0fee85
Closes-Bug: 1325379
Gerrit 2.8 uses a plugin to do replication and the command to trigger it
is different than the built in command from 2.4. Update the docs to
reflect the correct command.
Change-Id: I4b97a94a932b469a72eb3141ebd340785577465c
Currently the process for making a Third-Party CI system voting
is not documented. This patch documents the current ideal process
for moving a Third-Party CI system from the non-voting permissions
group to the voting permissions group in Gerrit.
Change-Id: I762aec397f1c0c26bab62fbcb124e8b002066a43
* doc/source/gerrit.rst: When project names change, Gerrit's lucene
indexes must be rebuilt while the service is still offline. If this
is not done, searches on the new project names will not find
existing changes and Zuul will ignore some events for them.
Change-Id: I99cd657298e05f7c213cf770e92d06016043f547
The nodepool documentation now builds and is published on
ci.openstack.org. Link this to the OpenStack infra
documentation for nodepool.
Change-Id: I8a2e4eece4f40846f927be6b0efb9d9afd1701fb
A much awaited feature, this patch is the outcome of running:
find modules/openstack_project/files/gerrit/acls/ \
doc/source/stackforge.rst -type f -exec sed -i -e \
's/^\(.* \)label-Workflow .*\(group .*\)$/\0\n\1abandon = \2/' \
-e 's/.*exclusiveGroup.*Workflow.*/\0 abandon/' \
{} \;
Change-Id: I217a8689528d14c9143de5656db01549f263c3b4
Closes-Bug: #1248794
Project acls in the refs/tags/* stanza should specific the ptl
of a program/project as opposed to all the core reviewers. This
patch changes the stackforge acl example to reflect this.
Also this patch changes WIP to Workflow in the explanation below
which is more consistent with Gerrit 2.8 functionality.
Change-Id: If7df749b54d5ace8904ea1def900618a196aa265
Puppet board has replaced puppet dashboard. Remove reference to puppet
dashboard as it shouldn't be used.
Change-Id: I5eeee2984729ef5d1b883b4762347d19786e28ed
We'd like to be able to control sequencing of how and when puppet
runs across our machines. Currently, it's just a set of agents
that run kinda whenever they run. At times they hang and we don't
know about it. Also, cross-server sequencing is impossible to
achieve.
Change the operation away from agents running on the machine as
daemons, and instead ssh from the master to each machine.
Change-Id: I76e41e63c6d0825e8735c484ba4580d545515e43
Add a link to the regex's for comment formatting and an example of how
to format test results nicely
Change-Id: Id917161ccf5e51855acf87a87544882dcf69b14e
This allows hiera data to be split into two buckets: sensitive and
non-sensitive. Sensitive data is put where it always has been. Non-
sensitive data, such as users ssh keys and lists of packages can be
put into the data directory contained within the
openstack-infra/config git repository.
This also introduces a more complex hierarchy: data is now split on
osfamily and lsbdistcondename. Operatingsystem is left for
compatibility.
Change-Id: I3b3faeab837aa5732da01e96bbe0c19aa936a58d
Stackforge creation sometimes includes source repos with crufty
branches. Cleaning these branches in stackforge requires -infra
core intervention. Sanitising them prior to seeding the stackforge
repo is easier than cleaning them afterward.
Change-Id: I0d71c9e252913dc781632988df95cc79c626d2b4
The "noop" job is the new internal noop job, unlike gate-noop which
actually ran a job on a test worker. This should save some test
resources.
Update stackforge documentation to match.
Change-Id: I6fa6fdc923bb2b966015cd74a1ecbe4a8d86ffaf
We require channels to be registered and have the openstackinfra
account added to the access list before we'll add infra-managed
bots.
Moving this documentation to the beginning of the document and
giving them their own section in case we wish to have other
requirements in the future.
Also add link on stackforge.rst back to the IRC page.
Change-Id: Ic92f3935de19c4afef23f51257a189f2860796c2