[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
Benjamin Kemper commented on JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds Thanks! I've used the RC and it did the trick. When is it expected to be released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
Benjamin Kemper resolved JENKINS-16659 as Fixed TriggerBuilder builds based on parameter value should be listed as downstream builds Fixed in 2.17-RC. Change By: Benjamin Kemper (21/Feb/13 3:27 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds with parameters should be listed as downstream builds
Benjamin Kemper created JENKINS-16659 TriggerBuilder builds with parameters should be listed as downstream builds Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 06/Feb/13 9:25 AM Description: This is similar to issue #11082, issue #9263, issue #5184. The only difference is how the "Projects to build" value is set. In my case I build an environment variable "$TO_TRIGGER" dynamically and simply put it in the text box, "parameterized trigger" does the job of expanding it to the job names well. The only problem is that although the projects are triggered and in the console log it is listed as if they were triggered successfully, see log: Waiting for the completion of trigger1 trigger1 trigger1#2 completed. Result was SUCCESS Build step 'Trigger/call builds on other projects' changed build result to SUCCESS Finished: SUCCESS They still don't appear as downstream builds, nor do they upstream build appear as upstream build in the downstream build. Project: Jenkins Priority: Major Reporter: Benjamin Kemper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
Benjamin Kemper updated JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds Change By: Benjamin Kemper (06/Feb/13 9:28 AM) Summary: TriggerBuilderbuilds withparameters basedonparametervalue shouldbelistedasdownstreambuilds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15737) MultiJob plugin does not take account current parameters
Benjamin Kemper commented on JENKINS-15737 MultiJob plugin does not take account current parameters I have encountered this also on 1.6. Downgraded manually to 1.5 and it works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
Benjamin Kemper commented on JENKINS-12966 gitTool crashes Jenkins startup Thanks Michael, I manually installed scriptler 2.4.1 and it solved the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
Benjamin Kemper commented on JENKINS-12966 gitTool crashes Jenkins startup It is happening to me also on 1.489. Stack trace: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:894) at jenkins.model.Jenkins.init(Jenkins.java:796) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) ... 13 more Installed plugins: LDAP Plugin pam-auth ant javadoc Jenkins Subversion Plug-in Jenkins jQuery plugin Jenkins jQuery UI plugin Nested View Plugin Jenkins Multijob plugin Token Macro Plugin Jenkins SSH Slaves plugin Python Plugin Jenkins CVS Plug-in Maven Integration plugin Copy Artifact Plugin Log Parser Plugin ChuckNorris Plugin Jenkins Translation Assistance plugin Green Balls Jenkins Parameterized Trigger plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
Benjamin Kemper commented on JENKINS-12966 gitTool crashes Jenkins startup Michael, I tried your suggestion and downgraded the CVS plugin to 2.6 and it still happens. Also tried downgrading the SVN plugin also just in case. I'm trying to install the Dynamic Parameter plugin which requires and installs the git and the scriptlr plugins, maybe one of them is the cause? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
