![]() |
|
|
|
|
Change By:
|
Alex Clifford
(03/Feb/15 5:23 AM)
|
|
Description:
|
Since updating a few minor versions to the latest I've noticed that when saving a Project's Configure page existing XUnist post-build actions get cleared and will not accept the values submitted.
The config.xml for a working project has the following for the xunit section:
-----
{code:xml}
<xunit plugin="[email protected]">
<types>
<PHPUnitJunitHudsonTestType>
<pattern>sstesting/logs/testsuite.xml</pattern>
<skipNoTestFiles>false</skipNoTestFiles>
<failIfNotNew>true</failIfNotNew>
<deleteOutputFiles>true</deleteOutputFiles>
<stopProcessingIfError>true</stopProcessingIfError>
</PHPUnitJunitHudsonTestType>
</types>
<thresholds>
<org.jenkinsci.plugins.xunit.threshold.FailedThreshold>
<unstableThreshold></unstableThreshold>
<unstableNewThreshold></unstableNewThreshold>
<failureThreshold></failureThreshold>
<failureNewThreshold></failureNewThreshold>
</org.jenkinsci.plugins.xunit.threshold.FailedThreshold>
<org.jenkinsci.plugins.xunit.threshold.SkippedThreshold>
<unstableThreshold></unstableThreshold>
<unstableNewThreshold></unstableNewThreshold>
<failureThreshold></failureThreshold>
<failureNewThreshold></failureNewThreshold>
</org.jenkinsci.plugins.xunit.threshold.SkippedThreshold>
</thresholds>
<thresholdMode>1</thresholdMode>
</xunit>
-----
{code}
If I edit an existing project or clone our template to a new Project this section gets replaced with:
-----
{code:xml}
<xunit plugin="[email protected]">
<types/>
<thresholds>
<org.jenkinsci.plugins.xunit.threshold.FailedThreshold>
<unstableThreshold></unstableThreshold>
<unstableNewThreshold></unstableNewThreshold>
<failureThreshold></failureThreshold>
<failureNewThreshold></failureNewThreshold>
</org.jenkinsci.plugins.xunit.threshold.FailedThreshold>
<org.jenkinsci.plugins.xunit.threshold.SkippedThreshold>
<unstableThreshold></unstableThreshold>
<unstableNewThreshold></unstableNewThreshold>
<failureThreshold></failureThreshold>
<failureNewThreshold></failureNewThreshold>
</org.jenkinsci.plugins.xunit.threshold.SkippedThreshold>
</thresholds>
<thresholdMode>1</thresholdMode>
</xunit>
-----
{code}
Our builds then fail because we require the test report to be written.
The workaround is to edit the correct values back into config.xml on the Jenkins master server and reload the configuration. It seems like the web interface's interaction with the REST API is breaking for this particular post-build action.
Any thoughts>
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
