Move remaining examples to unit tests, remove unnecessary '\' and align
docstrings to the predominate standard throughout the project.
Fix broken authenticated-build highlighted by the added unit test.
Change-Id: Ic9700f587073946be17be543920a4a3ed7cd19d0
If the user does not specify a "dirmatch" setting to JJB when using the
workspace-cleanup wrapper, JJB will default the "dirmatch" setting to
False.
Update the docs to describe this default. (This matches the post-build
workspace-cleanup publisher's docs.)
Change-Id: Ib4aa26f68a128038a70b88ccf0d8ba798614d5c5
On Fedora 24, the mavenName vs group XML is sorted differently depending
on whether we're using Python 3.5 or Python 2.7. This was causing the
test to fail on Python 3.5.
Avoid relying on the dict sort behavior. Since there are only two XML
elements, write each one explicitly.
Change-Id: I53f88e53d7fc4d81e325b341b9444c4950044565
Standardize the docstrings as much as possible in the builders module to
provide good working examples to be followed. Remove unnecessary use of
'\' to reduce copy 'n' paste and convert last remaining inline example
to unit test and include inline into docstring.
Change-Id: I02fe217f3a122aaac4d770e638011144236285cb
This change breaks our run-tox usage, see the compare-xml output.
This reverts commit 2de4ba8a8129365991fcabcc16ca8e91b08ed8e1.
Change-Id: I5ee2afd4f15d22d43eb78fe3086109fabb550e36
The entry point cucumber_testresult is incorrect given the style
adopted for all the other entry points, it should be:
cucumber-testresult=jenkins_jobs.modules.publishers:cucumber_testresult
Change-Id: I60fcecb667cb5aa626e9ca7b9dcaa3dba3122cfa
This change https://review.openstack.org/#/c/211993/ made '' an
invalid attribute value for pollscm, but that is a valid value. We use
'' for pollscm with the option to build when a changed is pushed to
github. This might have changed since we set it up, but you had to
specify a blank poll schedule for jenkins to build on pushes to github.
This changes allows '' as a valid value.
Change-Id: I35c45b4619584b3358562131399fc5ef16c4c5ec
This builder uses the ShiningPanda plugin. It is implemented as a "tox"
builder independent of the "shining-panda" one since the latter defines
"common" arguments (such as `nature` or `command`) that do not apply to this
tox builder.
Change-Id: I99c1fdad392d41deb9c8fdd5c3617bb10860ac39
Allows for use of regular expression conditions in the conditional
publisher plugin. Exposes two new fields: condition-expression and
condition-searchtext.
Change-Id: Ib752d686f009ca5687956622e22ee466c6791695
There's a relatively new workflow plugin, based on the old build flow
one
Change-Id: I5541443e15335839754afee59f1b74ed29ce6676
Signed-off-by: David Caro <dcaroest@redhat.com>
In complex configurations it may be useful to have a template
print out its name so that a given job can be easily traced to
its definition.
Change-Id: I1cfed9c27a58b45ba48aeed04839bfc8f54a831e
Where n = number of variables in scope for a particular job template instance.
and m = number of job template instance.
Let's imagine for a large set of jobs with n = 100 and m = 50
This debug message makes it difficult to scan through JJB output looking for
signficant debug messages and does not provide a clear value.
It is trivially easy to know which variables are and which are not included in a
job-template's name by simply reading it.
Change-Id: I745e26ac6062277fc477cb1ca70cf2809f5806e3
Prior to this patch macros serialized into a yaml document, a simple string
substitution was applied and then they were re-loaded into python. This
created several problems:
- newlines are lost because the yaml loading was not respecting the
newline settings of the original strings (Story: 1387060)
- {obj:} notation was not working for macro parameters (Story: 2000254)
- multiline strings passed into scripts will create a yaml syntax error
when being re-loaded (unticketed)
This patch resolves these problems by replacing the previous interpolation
code with the more robust `deep_format` method. A side effect of this patch
is that there are now fewer disparate code paths for interpolating variables.
Change-Id: Ia06c98286537a50dc52c6e5e000b32ebc9e8ede2
Signed-off-by: Justin Stoller <justin.stoller@gmail.com>
* Accept integers for threshold
In documentation is written that threshold should be integer.
But it fails with integer to generate XML.
Only case when it pass is for 0, because XML formatter consider it as
empty body and do not format it.
* Fix documentation for missing threshold field, plus test.
In documentation it says that missing threshold is set to 0, but apparently
it is set to Null (empty field), and it has different behaviour than for 0
value.
Change-Id: I326cbadd955c4c28f315fa72293d9a54a116b140
The docs say to use default-node while the code checks for
default-slaves. This results in no actual output if you
specify default-node in your job config. Changing to
default-slaves fixed the issue because thats what code is
actually checking.
Change-Id: Ifadfbe3f2c3ad027b348acdd00058109811ba232