the perform method should be passing the loop-variable 'moduleBuild' to ... #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to tdp.getTestData
|
plugins » maven-plugin #42 UNSTABLE |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
oleg-nenashev
approved these changes
Feb 6, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From the junit-attachements plugin we see a contradiction between the
The TestDataPublisher (without this change) is given a MavenModuleSetBuild. But when inside the hudson.tasks.junit.TestResultAction.Data.getTestAction(TestObject) calls hudson.tasks.test.TestObject.getOwner() it is given a MavenBuild.
When looking at this for loop in MavenTestDataPublisher it seemed natural to pass getTestData the moduleBuild. Otherwise the TestDataPublisher.getTestData is being called with the same MavenModuleSetBuild instance moduleLastBuilds.values().size() times.
The amount of testing I've done upon this change could only be described as anecdotal. Targeted unit tests may be required.