Skip to content

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.

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 kamilszymanski force-pushed the junit-publish-on-empty-reults branch from a9095a0 to 34d09b7 Compare February 9, 2016 07:32
@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