Pytest makes each scenario into individual selectable test.
To be able to run each scenario separately is very useful for development.
Change-Id: I4b1c990a1fd839ce327cd7faa27159a9b9632fed
Job DSL plugin supports execution of its groovy DSL code
via sandbox, but until now there was missing option to control it.
Change-Id: I8dccfc608cf59ac46ded712dc937983a22b9d3b3
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>
System groovy has difference with the simple groovy command. System
groovy result XML for system groovy command (script), looks like this:
<hudson.plugins.groovy.SystemGroovy plugin="groovy@2.3">
<source class="hudson.plugins.groovy.StringSystemScriptSource">
<script plugin="script-security@1.75">
<script>Groovy command</script>
<sandbox>[true|false]</sandbox>
<classpath>
<entry>
<url>...</url>
</entry>
...
<entry>
<url>...</url>
</entry>
</classpath>
</script>
</source>
<bindings>...</bindings>
</hudson.plugins.groovy.SystemGroovy>
Change-Id: I85eb5848de2a817ab132559b53cbeb316931195f
Introduce 2 booleans in the Gradle builder section to support passing
parameters by System Properties and Project Properties
Change-Id: I0de1e20b85902263e0d83ccadd64d42fc2b37193
Implemented new parameter "disable-host-key-checking" to make the
"anbile-playbook" builder compatible with version >=1.0 of the ansible
plugin. The parameter defaults to "false" for security reasons (as the
plugin does).
The old parameter "host-key-checking" is still written to XML to keep
code working in a setup with plugin version <1.0. This has no impact
on newer setups because the plugin with version >=1.0 ignores the old
parameter value.
For same security reasons the default value of old parameter
"host-key-checking" was changed to "true" to "fix" older setups which
have the parameter not defined.
Change-Id: I4a592c1a4d6ba8bb4f365ce505296cf5c09f7e19
Task: 39789
Story: 2007678
It's helpful to have possibility to set `jobAlias` in case the
same job is used multiple times with different configurations.
Change-Id: Ic092c6b2f5d893e75ebce4aaebc7eaf88a8978a6
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 commit adds a parameter to the ansible builder, vault-credentials-id.
This maps to the element <vaultCredentialsId> in the resulting job
definition, and has been tested against the Jenkins Ansible plugin
v1.0.
Change-Id: I40cfd9225923b29c9d2714a60279f1c88f6cb88c
This adds the 'publish-over-cifs' action to the builders module.
It enables the "Send files to a windows share" build step,
provided by the "Publish Over CIFS Plugin".
Change-Id: I80cb2f86091ef53a284cf85a381294bbb6133010
This change allows for the user to specify the following checkboxes:
* Upload Bitcode?
* Upload Symbols?
* Compile Bitcode?
The plugin defaults to these checkboxes being checked, so I kept those
defaults here.
Change-Id: I727611fd2a70f2157b05d030ec296c74a5b214a8
New options include:
1. exclude
2. result-var-suffix
This update affects copyartifact in builders.py
Change-Id: I682a10be47f049fe457e5bc199aa50a5583958a7
Signed-off-by: Tan Heng Yeow <E0032242@u.nus.edu>
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
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>
Branched from my xcode-20 branch and rebased from master
and added support for xcode 9.1 now that the xcode plugin has been
released
Due to:
https://issues.jenkins-ci.org/browse/JENKINS-45509
Change-Id: Ibd0f4c82b5e8f37a9da335c57786eae5dc91aefb
This patch adds support for aggregated test results in the Jenkins
MultiJobProject plugin.
Change-Id: I5c98f7814d33a740d9a70b584e00d1aa5f50e0ea
Signed-off-by: Major Hayden <major@redhat.com>
Update tests for minimal and full types and update docs with default
and required options.
Change-Id: If9aaa35e2d7943b6a49f976db83d9f6cae82005b
Co-Authored-By: Thanh Ha <thanh.ha@linuxfoundation.org>
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
As for now, JJB lacks the ability to control the `Enable enhanced
logging` option of Parametrized Remote Trigger plugin.
This option allows the console log of the remote job to be printed in
the console log of the calling job.
This patch adds the option `enhanced-logging` to the `trigger-remote`
builder to control this checkbox.
The default value is set to `False` to keep the current behaviour for those
who do not need the logs.
Change-Id: I3d109603b4eb9ce247e5e6c4588053e1c61ba6ce
Currently there is no possibility to setup options for 'NodeJS Plugin'
https://wiki.jenkins.io/display/JENKINS/NodeJS+Plugin
But 'NodeJS Plugin' is widely used to get ability of executing JS in build step
So this patch introduces configuration options for 'Execute NodeJS script' build step.
Change-Id: Ie0a9863f235d4199a6de350036394b8d054eb1e9
This continues to support the current string form for job configuration,
as well as adding a form that supports a mapping. This mapping has two
keys: "command", containing the command to be executed (i.e. the current
string parameter); and "unstable-return", containing the exit code that
configures the exit code that should cause a build to be marked
unstable.
Change-Id: I43ecc883236bbf8fc6de7ed8992e6d90da7d48ac
Also update code to use convert_mapping_to_xml helper.
Change-Id: Ie41c21dae7cd7367c2b24d9c1b5b0132572e784f
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
Currently multijob build step has no support for executionType
parameter added in 1.22 version of Multijob plugin.
This parameter allows to specify strategy for triggering build steps
inside multijob stage and this strategy could be parallel (which
is default and only supported version) or sequental.
This patch fixes this problem and adds corresponding parameter
"execution-type" for such build step.
Change-Id: Ie139da844a64b1591b05ccacb7e107fa07bd218a
When multiple steps are used, the condition has the wrong kind of
conditional and is always "Always".
Add test that exercise multiple steps with a And condition.
Also add a dummy test when multiple steps are listed.
Fix https://storyboard.openstack.org/#!/story/2000594
Change-Id: I4802bec9db407a09b23eea7e31235136d8bb72c2
- Added the following for builder and publisher
- Added all the fields for JMS Messaging plugins
- Added a minimal example
- Added a full example
- Added info in trigger for builder description of the plugin
Change-Id: Ifa209978dd38692da9f9d06bdf34782bd684a324