It turns out that we pass a lot of args around simply for the
purpose of doing mirror selection. This goes away if everything
gets a mirror.
This change should only be merged after the parent change has
propagated to all puppeted slaves and updated nodepool images.
Co-Authored-By: Jeremy Stanley <fungi@yuggoth.org>
Change-Id: I4a721f6559d7160c8213268a8c1e35c667a67a4f
Adding some extra verbiage to the docs to better explain how
the message tags tie in to telling logstash how to parse things.
Also noting which file to edit when adding new files, how to add
new parsing patterns, and some troubleshooting tips.
Change-Id: Ie91effd4b3ff3627ec040eb5c54b972e82add0e7
The parent patch of this dependency has an errant whitespace. This
patch removes that whitespace.
Parent patch: https://review.openstack.org/#/c/101013/
Change-Id: I96c0d5822b6b51891fea105aaf37f31059fc75b9
This patch fixes several nested bullets and other formatting problems
in the Requirements section of third_party.rst.
Change-Id: Ia071e87177b25f9b63cf185c932f0d29ebd3a475
Logging of meetings and channel is handled by the Supybot, update
documentation to explain both logging mechanisms and how to add
channel logging to the configuration.
Change-Id: I0e7f53f3699cc3352dbbe31379d4753d291a3c9d
This change compltes the documentation about how to create a new IRC channel
for a new project.
Change-Id: I284a292d653a5eb464be2d43cccb459334227c94
Closes-Bug: #1349823
The gate jobs already publish the specs as drafts and it
would be very beneficial to actually see those online at a permanent
place - rather than going to github.
This patch:
* Sets up a new site specs.openstack.org
* Creates new job-template '{name}-publish-specs' for publishing specs
* Creates new specs-job job-group for gating and publishing specs
* Converts all *-specs repositories to use the new job-group
* Creates Zuul specs-job macro to use these jobs
* Replaces those *-specs repositories that use already docs and python27
gates to use the new job-group and thus get published.
The patch does not take care of publishing of repositories that do not
use both the docs and python27 gates, this will be done separately.
implements bp publish-specs
Co-Authored-By: Andreas Jaeger <aj@suse.de>
Change-Id: Icc1c780cea8cd24c7a108429f84b2450056c6eed
At the QA/Infra sprint we decided that we're getting pretty
minimal value from asking people for bugs # in the tool, as we're
not really using that information. Instead, just convert to a
'recheck' string, which can include an arbitrary comment after it,
so that if people want to provide us with info, we can get it
out later, but it's no longer mandatory.
Change-Id: I419b0edf2e1805adbdba83b2630b087c7eaf14d9
Currently we instruct account requests to identify a name. This
has gotten problematic. This patch changes the account request
instructions to detail company name and product being tested so
that the Infrastructure team can create a name from this
information.
Change-Id: Ia3f3a893bcdb67f81ebdf05506e2880c0c5b1a5c
Currently some third party ci systems offer their logs as a tarball
requiring download. This patch adds some details about logs
specifying they must be browsable.
Change-Id: Ic3338074bbd8dd4c83434c7cb49d88e1d38e7293
Update footer for ci.openstack.org for copyright and clarification
as to what repo to edit for the documentation.
Change-Id: I0466827a66e800fb1d20f1508cf2e6ffe1b8369e
Big rewrite of the devstack-gate documentation to reflect the
work it does now and what it's passing off to Nodepool.
Change-Id: I8a432b7f60467de8deb70d9992f0ecafd4b3c8f7
We use bandersnatch to mirror pypi now and that should be documented.
Add all the usual header information with quick links to useful places
like local config and upstream bug trackers. Also, note how we run
bandersnatch and details on detecting and correcting stale packages on
pypi preventing local syncs.
Change-Id: I98db04c19c427335a4786a7923982fabcf57051b
Currently we disable mis-behaving third-party ci systems for a few
reasons and include the right to do so at -infra discretion.
This patch adds that fact to the documentation.
Change-Id: I9b8a66eadd9c6c7c2568e3cf408f64075d9a40fe
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
