Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for allowEmptyResults option in JUnit Plugin #734

Merged

Conversation

kamilszymanski
Copy link
Contributor

No description provided.

@jenkinsadmin
Copy link
Member

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

@@ -153,6 +153,7 @@ class PublisherContext extends AbstractExtensibleContext {
testResults(glob)
keepLongStdio(junitContext.retainLongStdout)
testDataPublishers(junitContext.testDataPublishersContext.testDataPublishers)
allowEmptyResults(junitContext.allowEmptyResults)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will break compatibility for everyone using an older version of the JUnit plugin. The new element should only be generated when a minimum version of the plugin is installed, e.g.

if (jobManagement.isMinimumPluginVersionInstalled('junit', '1.10')) {
    allowEmptyResults(junitContext.allowEmptyResults)
}

@drwoods
Copy link
Contributor

drwoods commented Feb 8, 2016

Conflict mentioned above is in docs/Home.md -
<<<<<<< HEAD

* Removed anything that has been deprecated in 1.36, see Migration

Merged the pull request into my local branch, built, deployed on Jenkins 1.625.3 w/ the junit-1.10 plugin and verified the patch works in a job that generates other jobs via DSL and includes the new allowEmptyResults option.

@kamilszymanski
Copy link
Contributor Author

rebased on master

@daspilker daspilker merged commit 34d09b7 into jenkinsci:master Feb 11, 2016
@kamilszymanski kamilszymanski deleted the junit-publish-on-empty-reults branch February 11, 2016 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants