When we use zuul:value to xref, the default title text for the link
is the full target name (eg "pipeline.trigger.github.event.pull_request")
which is a bit verbose. Normally, we would just want the final element
as the title for a value (so a sentence might read "When a <pull_request>
event is received...").
Change-Id: I42cd678d9bb97058d5fbe255791cbc476d5057bb
At some point, we changed 'image' to 'label' and missed that in
the docs. Also correct a misspelled word.
Change-Id: Ie0e6ef8cc9eafe9b5353a07e6d11b6c67580b77a
This is not complete, but it's a start.
While doing this it became clear that the upstream csvfile lookup plugin does
not work in python3. Work around that by putting in a simpler version of
the code into our copy.
Change-Id: Ic84d8265e6fd7e15a0e5d66c781409a087d761d7
The merger process does not use the state_dir, remove the check
that it exists. It was already undocumented, so this now matches
the documentation.
Change-Id: Ie8cbe75ce4dff774b3f5b3bdaaf324fd9ba6698f
This updates common and scheduler.
Also adds a note to the docs style guide about booleans because
I was reminded of it while I was updating this.
Change-Id: I56b3e3c8f99548887056b881f9b3d77e9f45b275
This change:
* fixes some spelling issues
* externally links to a document describing what a 'git ref' is
* links to executor document at the first reference to it
* links to independent pipeline at the first reference to it
Change-Id: I3f2247deac15fd15c9dead6cba537d7b17e8491f
The FakeGithubConnection redefines the methods getCommitStatuses and
setCommitStatus for test purposes. This implies that the original
methods of GithubConnections are untested. This is an attempt to
remove these from FakeGithubConnection and pushing the test handling
into a FakeGithub object. This way we can do the test handling and at
the same time use the original methods of GithubConnection.
This also uncovered some test fixtures which are invalid in Github
context as there projects require the form <owner>/<project> which is
not matched by the 'common-config' which was used in many fixtures.
Change-Id: Ib3badca63b77166c1d69332121d78ef05bd899fe
When using a branch and pull model on a shared repository there are
usually one or more protected branches which are gated and a dynamic
number of temporary personal/feature branches which are the source for
the pull requests. These temporary branches while ungated can
potentially include broken zuul config and therefore break the global
tenant wide configuration.
In order to deal with this model add support for excluding unprotected
branches. This can be configured on tenant level and overridden per
project.
Change-Id: I8a45fd41539a3c964a84142f04c1644585c0fdcf
We were incorrectly preparing the current state of the repo for
ref updated (eg, post) jobs. This ensures that we run with the
actual supplied ref, even if the remote has moved on since then.
Change-Id: I52f05406246e6e39805fd8365412f3cb77fe3a0a
This adds a directive (and role) for zuul variables, which also
have a complex hierarchy like configuration values.
The type field may be used to cause, for example, 'items' to render
as 'items[]' to remind users that they must provide an index. It
is ignored for the purposes of the cross-reference role, indices,
and link targets.
Change-Id: I674b17d8257c501cfc5c2f29f2aab9804e9ec846
James E. Blair