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 MultiJob plug-in issues #265

Closed
orangemocha opened this issue Nov 24, 2015 · 6 comments
Closed

Jenkins MultiJob plug-in issues #265

orangemocha opened this issue Nov 24, 2015 · 6 comments

Comments

@orangemocha
Copy link

Version 1.19 of the plug-in introduced a bug for which the setting "Build only if SCM changes" is reversed. https://issues.jenkins-ci.org/browse/JENKINS-30952

@joaocgreis worked around this by flipping the setting in all the node-test-* jobs. #232 (comment)

Version 1.20 introduced yet another bug that leads to a NullPointerException in some cases: https://issues.jenkins-ci.org/browse/JENKINS-31527. See #263 (comment) for a few examples of failures in our CI.

It is unclear whether 1.20 solves the issue about the SCM polling setting.

I downgraded the plug-in to version 1.19. I suggest we stick to this version until the above issues are fixed in the plug-in.

@orangemocha
Copy link
Author

/cc @nodejs/jenkins-admins

@jbergstroem
Copy link
Member

So, in the spirit of forking, does anyone want to take a stab at fixing these so we can get the "build if scm changes" fix?

@rvagg
Copy link
Member

rvagg commented Feb 2, 2016

screen shot 2016-02-02 at 4 09 58 pm

https://github.com/jenkinsci/tikal-multijob-plugin/commits/master

They appear to think they got that build condition thing sorted out in 1.20.

As for the NPE, I'd love to see the errors we had in #263 (comment) but the logs are now gone cause of auto-cleanup. If it's the same stack-trace with the same line# as in the JIRA report then it'd be from https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java#L170 which hasn't changed since 1.20 but I'd like to confirm that. It'd be to do with lastJob not having a workspace for getWorkspace() and probably wouldn't be hard to fix but we'd need a failure case to be able to test it.

Unfortunately this all means upgrading the plugin, trying it out, understanding where our breakage is and fixing from there.

@jbergstroem
Copy link
Member

We have all old jobs at the backup server. I'll try and find something around when the dates when we complained.

@joaocgreis
Copy link
Member

Finally fixed by #775 . I hope we don't end up with some different issue like in 1.20.

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

No branches or pull requests

4 participants