Add support for the following configuration options:
- stripSingleParents
- flattentTapResult
- skipIfBuildNotOk
- removeYamlIfCorrupted
Signed-off-by: Kienan Stewart <kstewart@efficios.com>
Change-Id: I387e5cd46fadb54e478627346dc6b4223bda1fc0
Pytest makes each scenario into individual selectable test.
To be able to run each scenario separately is very useful for development.
Change-Id: I4b1c990a1fd839ce327cd7faa27159a9b9632fed
This change adds support for git publisher rebase before push. [0]
[0] https://plugins.jenkins.io/git/
Signed-off-by: Zhang Xiaoxu <zhangxiaoxu5@huawei.com>
Change-Id: I3cb0eecbbee6c51433cb4e3b856a3165462f49d1
This new option has been added in JUnit v1.51
https://github.com/jenkinsci/junit-plugin/releases/tag/junit-1.51
The user can decide not to mark a build as unstable on test failure.
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Change-Id: I960ed98cf4b0f8f632546492f6dbb6d1aa0055c9
This new option has been added in JUnit v1.39
https://github.com/jenkinsci/junit-plugin/releases/tag/junit-1.39
The user can decide not to publish issues to SCM provider platforms.
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Change-Id: I543dbd5cb355acc5106336afd8953a03245df2fa
A new major version (3.0.0) of XUnit plugin has been released in January
2021:
https://github.com/jenkinsci/xunit-plugin/releases/
I didn't have an issue when I upgraded the plugin from version 2.4.0 to
3.0.0. But I started to have this error at the end of a build and I
guess it appeared only after having modified the configuration of the
Jenkins jobs with JJB:
ERROR: Build step failed with exception
java.lang.IllegalArgumentException: The tools section is required.
at org.jenkinsci.plugins.xunit.XUnitProcessor.<init>(XUnitProcessor.java:139)
at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:204)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:80)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:803)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:752)
at hudson.model.Build$BuildExecution.post2(Build.java:177)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:697)
at hudson.model.Run.execute(Run.java:1932)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Publish xUnit test result report' marked build as failure
When looking at the configuration of the job from the Web UI, the XUnit
plugin was enabled but left "unconfigured": no file to look at.
Apparently, JJB is sending a XML config that is not understood by XUnit
plugin anymore. I guess I didn't have any issue before updating the
Jenkins jobs with JJB because when upgrading XUnit plugin from 2.4.0 to
3.0.0, Jenkins migrated the config to the new format.
From what I see when analysing the generated XML from JJB and the one
from Jenkins after having configured a job manually, a sub-element has
been renamed, from 'types' to 'tools'. I suspect this is caused by this
commit:
https://github.com/jenkinsci/xunit-plugin/commit/aa47ac57d
(XUnitBuilder class had this line: @XStreamAlias("types"))
So here, I simply picked 'tools' or 'types' for the sub-element and
depending on the plugin's version in both the builder and the publisher
parts. I'm only using the publisher but I guess the problem is the same
with the builder.
Tests have been adapted to verify both versions <3.0.0 and >=3.0.0.
Change-Id: Ie78539d0ae25ddc139ad9982cdffd2e683dd40b2
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
The join-trigger documentation still uses the deprecated
"even-if-unstable" field in its examples.
Update the "join-trigger001.yaml" fixture referenced by the
documentation to use the "threshold" configuration instead.
Add a new fixture to retain coverage for "even-if-unstable".
Change-Id: Ic8b28b384e0a6d7e43833d2db9524a41e4508ba7
Add support for custom messages per build result in the Slack
notification plugin.
Change-Id: Iafc8b67528914c6d14c78f72aa535a3cfa7f7033
Story: 2007912
Task: 40315
Parameters inside triggers were not updated while the upper
parameters were changed, were staying as default. Updated
the implementation to make it take from the upper level.
Change-Id: I16fc3525fcdf0a8bf3aea3b8422f0f2ad26f9e24
Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
Added also a test case for version specific changes
Change-Id: I5213dccffc441037c63ee7c042aee4a8a84d9732
Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
Updated test cases as well, The tag has been introduced after 2.35.2
therefore the parameter is also >=2.35.2
Change-Id: Ie0801108a16969b420b341e2deaa6ba62deb116c
Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
The joinTrigger plugin now accepts a resultThreshold field instead
of the evenIfDownstreamUnstable boolean. Add support for a "threshold"
yaml field to manage this value.
Change-Id: I60ba999b963709a76854a4d50387d2b1eefae05f
Signed-off-by: David Aguilar <davvid@gmail.com>
Add support for the recipient item "Upstream Committers" of the
"Send To" list of a trigger of the "Email Extension" (email-ext)
plugin.
Change-Id: Iaa77330bb1910881df154494b0472ce21ea28d99
Task: 39595
Story: 2007607
executeOn setting is available for PostBuildStep
since 2.0 version of the Post Build Script plugin.
For previous plugin's version executeOn should be
set on the PostBuildScript layer.
Change-Id: I6b7c9ccfbd0a2d610499074675835e6b5d96cb17
Task: 39028
Story: 2007411
Please review the following patch containing the code changes in
the repo. This patch is a transition patch and is the auto-generated
output of the python-black tool.
Change-Id: I2d2de71da8a105fb62b561899ae78441ddab4032
Signed-off-by: Thanh Ha <zxiiro@gmail.com>
This adds the 'publishers-from' action to the publishers module.
It enables the "Use publishers from another project" provided by
the "Template Project Plugin".
Change-Id: I6fb030a99bccaa79e4f99efe012ff63c6d376a38
The publish-over plugins all expose the option 'verbose' to all for
lots of debug output from the connection to be outputted to the jenkins
console. However by default this is supposed to be disabled ('false')
so update the existing code to switch to the correct behaviour.
Change-Id: Ie9acb1a005a25cd5c9f279cc89d5178eb8d54dd7
1. Refactored the code in the function to utilize convert_mapping_to_xml's
way of detecting valid types.
2. Refactored optional parameters to use convert_mapping_to_xml
Note:
This update will affect users using lowercase inputs in their YAML files.
An exception will be raised if the inputs doesn't follow the exact
casing required by the plugin.
Change-Id: I053ef5f58200e51b3f6ff5ec55760f9e6f095370
Preparatory move for adopting pre-commit hooks.
Shoudl only remove newlines and spaces at end of files.
Change-Id: Ia33679467c533722b9308f7e7b74be395c926428
Signed-off-by: Sorin Sbarnea <ssbarnea@redhat.com>
Currently we have only possibility to set build status on GitLab
But GitLab Plugin provides us to make a comments and to vote on Merge Request
* Add Gitlab Message - configure Gitlab publisher to post comments on MR
* Add Gitlab Vote - jenkins set Vote for build status on GitLab MR
Change-Id: I30d2fbed647763f2a5eb6fb801dd79f6d43d4696
Co-Authored-By: Kien Ha <kienha9922@gmail.com>
Signed-off-by: Kien Ha <kienha9922@gmail.com>
Update trigger-parameterized-job arguments, to include
trigger from child projects.
Closes-Bug: story/2002157
Change-Id: Iae0610ee942dd2cad95e3fcaa8b70b16f42b3c50
Allows you to explicitly set which sonar configuration to use
for the sonar analysis when having more than one sonar installation.
In this case you are required to select which one to use,
as there is no default fallback in the Jenkins plugin itself.
Also added a similar option for configuring the maven installation
to use. This does have a default value, the version used in the
maven build in the same job. However, if for some reason you
need a different version of maven for sonar analysis you
have to be able to configure which one.
Adds parameter installation-name for the sonar configuration,
and maven-installation-name for the maven configuration.
Change-Id: I013ea80688efa17334448e6394d312ca6854cf07