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

[JENKINS-49089] Whitelist problems #112

Merged
merged 4 commits into from
Jan 24, 2018

Conversation

jglick
Copy link
Member

@jglick jglick commented Jan 23, 2018

JENKINS-49089

  • at least get some tests running
  • find a way to make this code path be run in a test before saveing the build
  • make some ModuleDependency fields transient

@reviewbybees

@@ -53,7 +53,7 @@
* @author Kohsuke Kawaguchi
* @since 1.133
*/
final class SplittableBuildListener extends AbstractTaskListener implements BuildListener, Serializable {
Copy link
Member Author

Choose a reason for hiding this comment

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

… by accident in test sources and so of course never used!

Cf. e68ef92 by @kohsuke:
“Checking in my partial work on this issue.”
@jglick
Copy link
Member Author

jglick commented Jan 23, 2018

Bug introduced by jenkinsci/jenkins@e418e44 with the helpful commit message by @kohsuke

Massaging the pull request to simplify the code.

It seems to have been from jenkinsci/jenkins#542.

@jglick
Copy link
Member Author

jglick commented Jan 23, 2018

…which did add test coverage—but using mocks. Making it useless for actually detecting regressions like this.

@jglick
Copy link
Member Author

jglick commented Jan 23, 2018

…and the test has to be Ignored on newer cores anyway (as of #109), again due to use of mocks.

@jglick
Copy link
Member Author

jglick commented Jan 23, 2018

I tried to follow what the code here is doing, in an effort to craft a functional test which would trigger this code path, but could not do so after brief effort. I am not inclined to waste too much time working on this plugin; probably better to release a fix based on code inspection & reasoning, and hope it suffices.

Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

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

🐝 It should not make it worse at least

@jglick
Copy link
Member Author

jglick commented Jan 23, 2018

@reviewbybees done but not sure who normally releases this—@oleg-nenashev? @aheritier?

@oleg-nenashev
Copy link
Member

I have reached out to @aheritier to sync-up on that

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.

2 participants