[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
rsandell created JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth Issue Type: Bug Assignee: Sam Kottler Components: core, github-oauth-plugin Created: 26/Nov/14 9:58 AM Description: SEVERE: Executor threw an exception java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:542) at org.jenkinsci.plugins.GithubSecurityRealm$2.loadUserByUsername(GithubSecurityRealm.java:494) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:282) Environment: Jenkins 1.580.1 Project: Jenkins Priority: Major Reporter: rsandell 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/d/optout.
[JIRA] [core] (JENKINS-19584) Ability to redirect user to configuration screen when erroneous data is saved
rsandell commented on JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved According to the javadoc of FormValidation, hudson.model.Failure and hudson.model.Descriptor.FormException; throwing any of those should display a user friendly error page, perhaps tweaking those to be able to go back to the correct form state could at least approve things. Although when I try to throw a hudson.model.Failure I get the standard oops page instead of a "nicer" error page. 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/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-19582) GoogleCode browser URL must end with '/source/'
rsandell commented on JENKINS-19582 GoogleCode browser URL must end with '/source/' throwing a hudson.model.Failure should according to the docs display a more user friendly error page, but when I try that in my own plugin it just displays the oops page with full stacktrace anyways. 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/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24059) NullPointerException on non-existent downstream builds
rsandell closed JENKINS-24059 as Fixed NullPointerException on non-existent downstream builds Version 1.10.0 (released Sep 19, 2014) Change By: rsandell (19/Sep/14 1:50 AM) Status: Open Closed 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/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
rsandell closed JENKINS-17658 as Fixed Provide a token so that build failure causes can be included in build failure emails Version 1.10.0 (released Sep 19, 2014) Change By: rsandell (19/Sep/14 1:50 AM) Status: Open Closed 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/d/optout.
[JIRA] [core] (JENKINS-23378) Raise minimum requirement to servlet 3.0
rsandell commented on JENKINS-23378 Raise minimum requirement to servlet 3.0 I've been trying to get the support guys to upgrade our Jenkins env to tomcat7 for a while now, but we keep backing down to tomcat6 as soon as instabilities arise. So I'm for this change as it would force us to actually take the leap 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23152) builds getting lost due to GerritTrigger
rsandell commented on JENKINS-23152 builds getting lost due to GerritTrigger That's why I would like to see stop and start being called on triggers when reload from disk happens, there is no other hook for the trigger to realize that it is happening so that it can clear out the listeners list of old objects. 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23152) builds getting lost due to GerritTrigger
rsandell edited a comment on JENKINS-23152 builds getting lost due to GerritTrigger That's why I would like to see stop and start being called on triggers when reload from disk happens, there is no other hook, that I know of, for the trigger to realize that it is happening so that it can clear out the listeners list of old objects. 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/d/optout.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
rsandell assigned JENKINS-15156 to Unassigned Builds disappear from build history after completion Change By: rsandell (23/May/14 8:08 AM) Assignee: rsandell 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
rsandell resolved JENKINS-21067 as Fixed New server config not reachable if using a prefix in URL released in 2.11.0 Change By: rsandell (21/May/14 2:27 PM) Status: Open Resolved 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21036) NullPointerException in StreamWatchdog when trying to stop/restart
rsandell commented on JENKINS-21036 NullPointerException in StreamWatchdog when trying to stop/restart 2.12.0-beta-1 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22155) NullpointerException when loading dynamic config jobs when updated to 2.11
rsandell resolved JENKINS-22155 as Fixed NullpointerException when loading dynamic config jobs when updated to 2.11 Released in 2.11.1 Change By: rsandell (21/May/14 1:16 PM) Status: Open Resolved 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/d/optout.
[JIRA] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
rsandell commented on JENKINS-21520 NoClassDefFoundError in git client 1.6.1 Reverting to 1.6.1 fixed it for us as well, for a while. Then it happened again, in runtime, without a restart. We are also running 1.532.2 with all plugins updated to the latest version at the time of upgrade (so credentials plugin is in there as well). 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/d/optout.
[JIRA] [core] (JENKINS-22311) gerrit trigger can cause unwieldy build history when there are pending jobs
rsandell updated JENKINS-22311 gerrit trigger can cause unwieldy build history when there are pending jobs Change By: rsandell (25/Mar/14 9:26 AM) Assignee: rsandell Component/s: gerrit-trigger 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/d/optout.
[JIRA] [envinject] (JENKINS-22169) Migration from setenv overwrites existing envinject configuration
rsandell created JENKINS-22169 Migration from setenv overwrites existing envinject configuration Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 13/Mar/14 9:17 AM Description: If a job had both setenv and envinject configuration the "auto-migration" of setenv overwrites existing envInject configuration in the job. Project: Jenkins Priority: Critical Reporter: rsandell 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22155) NullpointerException when loading dynamic config jobs when updated to 2.11
rsandell commented on JENKINS-22155 NullpointerException when loading dynamic config jobs when updated to 2.11 This is due to the serverName not being fully migrated to the dynamic trigger config. e.g. serverName is null. 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22155) NullpointerException when loading dynamic config jobs when updated to 2.11
rsandell created JENKINS-22155 NullpointerException when loading dynamic config jobs when updated to 2.11 Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 12/Mar/14 5:07 PM Description: See the stacktrace Mar 12, 2014 5:37:05 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Gerrit_check_job java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerTimer.schedule(GerritTriggerTimer.java:87) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerTimerTask.(GerritTriggerTimerTask.java:44) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:352) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:110) at hudson.model.AbstractProject.onLoad(AbstractProject.java:327) at hudson.model.Project.onLoad(Project.java:90) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$18.run(Jenkins.java:2616) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:945) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Project: Jenkins Priority: Critical Reporter: rsandell 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/d/optout.
[JIRA] [core] (JENKINS-19584) Ability to redirect user to configuration screen when erroneous data is saved
rsandell commented on JENKINS-19584 Ability to redirect user to configuration screen when erroneous data is saved The git plugin is one such example. If the master isn't configured correctly for your git environment, but your slaves are (because it is not intended to clone to master or some other securinty measures) then the git plugin will complain that it can't find the repo, but it will clone just fine when it starts to build on a slave. That is probably an issue with the git plugin, but it is an example of a "false" error. 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/d/optout.
[JIRA] [subversion] (JENKINS-22090) svn-tag does not handle multi-configuration projects correctly
rsandell assigned JENKINS-22090 to k2nakamura svn-tag does not handle multi-configuration projects correctly not a multi-slave-config-plugin issue. Change By: rsandell (07/Mar/14 6:07 PM) Assignee: rsandell k2nakamura 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/d/optout.
[JIRA] [subversion] (JENKINS-22090) svn-tag does not handle multi-configuration projects correctly
rsandell updated JENKINS-22090 svn-tag does not handle multi-configuration projects correctly Change By: rsandell (07/Mar/14 6:06 PM) Component/s: multi-slave-config 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/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21878) jenkins-multijob-plugin
rsandell assigned JENKINS-21878 to Unassigned jenkins-multijob-plugin Reassigning; Not my plugin, it was originally (wrongfully?) set to one of my components. Change By: rsandell (19/Feb/14 3:48 PM) Assignee: rsandell 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-multijob-plugin] (JENKINS-21879) jenkins-multijob-plugin
rsandell assigned JENKINS-21879 to Unassigned jenkins-multijob-plugin Not my plugin, it was originally (wrongfully?) set to one of my components. Change By: rsandell (19/Feb/14 3:47 PM) Assignee: rsandell 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] [gerrit-trigger] (JENKINS-20098) GitClient.getRepository deprecated and broken
rsandell commented on JENKINS-20098 GitClient.getRepository deprecated and broken There is a beta version of 2.11 released since a bit over a month back. If you don't dare to run the beta then there is a special 2.10 branch with this fix in https://github.com/jenkinsci/gerrit-trigger-plugin/tree/git-client-fix 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] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
rsandell commented on JENKINS-21067 New server config not reachable if using a prefix in URL what prefix? 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] [gerrit-trigger] (JENKINS-19891) When configuring Gerrit project with file pattern, do not try to match COMMIT_MSG file.
rsandell commented on JENKINS-19891 When configuring Gerrit project with file pattern, do not try to match COMMIT_MSG file. Please provide a pull request instead of a patch file. 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] [gerrit-trigger] (JENKINS-19163) Use REST API for commenting on changes
rsandell commented on JENKINS-19163 Use REST API for commenting on changes In beta release 2.11.0-beta-1 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] [gerrit-trigger] (JENKINS-20225) Choosing strategy Gerrit trigger stopped working
rsandell commented on JENKINS-20225 Choosing strategy Gerrit trigger stopped working I did some fixes around this that is available in 2.11.0-beta-1 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] [gerrit-trigger] (JENKINS-19678) "Stop" button should stop all listeners
rsandell closed JENKINS-19678 as Not A Defect "Stop" button should stop all listeners Change By: rsandell (06/Dec/13 4:48 PM) Status: Open Closed Resolution: Not A Defect 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] [gerrit-trigger] (JENKINS-19364) Gerrit Trigger: make review category votes per job, not global
rsandell closed JENKINS-19364 as Not A Defect Gerrit Trigger: make review category votes per job, not global Change By: rsandell (06/Dec/13 4:46 PM) Status: Open Closed Resolution: Not A Defect 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] [gerrit-trigger] (JENKINS-19364) Gerrit Trigger: make review category votes per job, not global
rsandell commented on JENKINS-19364 Gerrit Trigger: make review category votes per job, not global It can do that. It is hidden behind the advanced button in the trigger's section on the config page of the job. 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] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
rsandell commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit Yepp, I just released 2.11.0-beta-1, it should be available in the experimental update center soon. And I am looking for brave beta testers to try it out 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] [gerrit-trigger] (JENKINS-12921) Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error
rsandell commented on JENKINS-12921 Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error It is the Git plugin that wants to add an env var to the build during checkout but fails at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) If you fill in a branch value in the git config section, you could put whatever you want here I think. I usually jut put in master, since the choosing strategy will check out a specific revision anyways. 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] [gerrit-trigger] (JENKINS-12921) Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error
rsandell updated JENKINS-12921 Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error Change By: rsandell (30/Jul/13 1:33 PM) Component/s: git 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] [gerrit-trigger] (JENKINS-18391) Gerrit Version is null after upgrade to 2.10.1
rsandell commented on JENKINS-18391 Gerrit Version is null after upgrade to 2.10.1 Also, 2.5 is the lowest version needed for all the current features; draft-published requires 2.5 and that is currently the highest check we have, so in your specific case it is not as bad that it can't find it. 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] [gerrit-trigger] (JENKINS-18391) Gerrit Version is null after upgrade to 2.10.1
rsandell commented on JENKINS-18391 Gerrit Version is null after upgrade to 2.10.1 Hmm, I hate to say it, but it works on my machine. I installed a Gerrit version 2.5 locally (upgraded from 2.3-rc0) and started Jenkins with Gerrit Trigger 2.10.2-SNAPSHOT (i.e. the same as 2.10.1) and it got the version correctly. Is it actually 2.5 or some micro version above, like 2.5.2 or something? 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-16868) Icons are not displayed with a reverse proxy
rsandell resolved JENKINS-16868 as Fixed Icons are not displayed with a reverse proxy Fixed in version 1.4.1 Change By: rsandell (14/Mar/13 4:12 PM) Status: Open Resolved 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-16868) Icons are not displayed with a reverse proxy
rsandell commented on JENKINS-16868 Icons are not displayed with a reverse proxy Commit: e4f7fb996be928c5fdb236a78e67e4350fcd512f 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-10709) multiple builds are triggered for one change in Gerrit
rsandell commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit I think the "posting configuration xml" feature is using the same code in core that reload config from disk is using, so yes it is a very likely it is a similar issue. When we had the bug in the past it was due to the way the GerritHandler (a class in the trigger plugin) was storing each listener i.e. each GerritTrigger instance to notify when an event arrives. And when reload from disk is performed Jenkins actually creates new instances of each job and for some reason the old job instance wasn't removed from the listeners list. We solved it by implementing the list as a HashMap with the project name as the key so when a project added itself twice the instance from the last invocation was the one saved in the map. But that caused a bug when a project was renamed, so that was fixed by using a Set instead I think, maybe that caused the original bug to reappear. Anyways; some hints on how the flow goes during startup might be of help to anyone wanting to dig into this bug. When Jenkins starts: PluginImpl.start() is called before any jobs are loaded. PluginImpl will instanciate a GerritHandler that handles the communication and stream-events coordination towards Gerrit. Then when each job has been loaded GerritTrigger.start() is called, and that will add the GerritTrigger instance as a listener in GerritHandler (via a call to PluginImpl.addListener). When a job is removed or unloaded GerritTrigger.stop is called and that will remove the GerritTrigger instance as a listener. The same happens when you reconfigure a job in Jenkins. When save is clicked first stop will be called on the old instance of GerritTrigger, then a new instance is created by Jenkins and start is called on that. So in theory everything should be fine, but something is handled differently when the config is changed from disk or other than clicking save in the UI. Maybe stop is never called or called in a different order so the old instance isn't removed. Or maybe it's a new bug completely (but probably unlikely). 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-10709) multiple builds are triggered for one change in Gerrit
rsandell commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit Reloading from disk has been a problem in the past. Other plugins have the same problem, but maybe not as visual as GT. It is not an easy thing to fix, not to keep being 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
rsandell assigned JENKINS-17008 to Unassigned Config changes stop Jenkins from running on next restart, stop/start, reboot. Change By: rsandell (05/Mar/13 7:10 AM) Assignee: rsandell 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-16851) Strategy GerritTrigger missing with git plugin 1.1.28
rsandell resolved JENKINS-16851 as Fixed Strategy GerritTrigger missing with git plugin 1.1.28 Released in Git Plugin 1.2.0 Gerrit Trigger Plugin 2.8.0 Change By: rsandell (21/Feb/13 3:31 PM) Status: Open Resolved 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-16851) Strategy GerritTrigger missing with git plugin 1.1.28
rsandell commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 Yes that looks very similar. 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-16851) Strategy GerritTrigger missing with git plugin 1.1.28
rsandell commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 I probably need to do some changes in the Gerrit Trigger as well, because the current code assumes that the IGitApi reference is something else (by casting it) so that it can do some log parsing. And with the new git api implementation that assumption is wrong. 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-16851) Strategy GerritTrigger missing with git plugin 1.1.28
rsandell commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 The git plugin beats me again I've managed to fix the incompatibility, and in the process I happened to fix the changelog issue in GT as well. But that introduced an infinite loop between the git plugin and Mailer in core when the culprits are being calculated at the end of the build. >From the looks of it it does not have to do with my changes, but I need to dive into it more before I let it loose in the wild. 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-15674) Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'
rsandell commented on JENKINS-15674 Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default' A similar thing happens for me on the Warnings Plugin, the settings for what parsers to use sometimes defaults back to the first available setting, it could be unrelated. Do you have similar issues as well? What core version and git plugin versions do you use? 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-16330) Trigger should start two jobs, but one is never started
rsandell commented on JENKINS-16330 Trigger should start two jobs, but one is never started Nothing in that list that I can find either. Could it be triggered builds that are on the same patch set number? The queue consolidates runs that have the same exact parameters as another scheduled task. That could be the reason the run is "lost". We fixed that in 2.6.0 by introducing a unique hash parameter for every triggered build. 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-16330) Trigger should start two jobs, but one is never started
rsandell commented on JENKINS-16330 Trigger should start two jobs, but one is never started Yes this is a tricky situation for the trigger; it needs to coordinate what jobs it has scheduled but (from what I can find) can't know if the job was canceled while in the queue, if that happens it will wait forever for the build to start (that's when it sends the build started message to Gerrit) Do you have any plugins that might cancel jobs in the queue? or maybe users that does it manually? 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-8226) Add reviewers in gerrit when a build is successful
rsandell commented on JENKINS-8226 Add reviewers in gerrit when a build is successful I did a new release anyways without this feature. Fingers crossed that it gets into the next one. 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-8226) Add reviewers in gerrit when a build is successful
rsandell commented on JENKINS-8226 Add reviewers in gerrit when a build is successful It's basically that feature I am waiting for before I make a new release. 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
rsandell commented on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration I tried to reproduce this on a clean Jenkins core v. 1.492 Installed Gerrit Trigger 2.6.0 And created a project; works Upgraded CVS Plugin to 2.7 and reconfigured the job; works Could it be something else in your combination that is causing it? 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-8562) Reloading Hudson Configuration Causes "Duplicate" Gerrit Jobs To Trigger
rsandell closed JENKINS-8562 as Fixed Reloading Hudson Configuration Causes "Duplicate" Gerrit Jobs To Trigger Fixed in version 2.3.1 Change By: rsandell (01/Dec/12 5:57 PM) Status: Open Closed 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
[JIRA] (JENKINS-10067) gerrit triggered job missing the retrigger option
rsandell closed JENKINS-10067 as Incomplete gerrit triggered job missing the retrigger option No answer from reporter. This should be fixed by other fixes. Change By: rsandell (01/Dec/12 5:51 PM) Status: Open Closed Resolution: Incomplete 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-8226) Add reviewers in gerrit when a build is successful
rsandell commented on JENKINS-8226 Add reviewers in gerrit when a build is successful https://github.com/jenkinsci/gerrit-trigger-plugin/pull/29 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-10224) Gerrit plugin doesn't work in current Jenknis version
rsandell closed JENKINS-10224 as Not A Defect Gerrit plugin doesn't work in current Jenknis version Haven't heard back from the reporter. Please re send if it still doesn't work for you. Change By: rsandell (01/Dec/12 5:47 PM) Status: Open Closed Resolution: Not A Defect 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-15888) Executing different build steps on different slaves in the same job
rsandell resolved JENKINS-15888 as Not A Defect Executing different build steps on different slaves in the same job This is more of a question than an issue, and should be directed to the users mailing list. But the conditional buildstep plugin is probably your answer: https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin Change By: rsandell (21/Nov/12 10:06 AM) Status: Open Resolved Resolution: Not A Defect 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-15888) Executing different build steps on different slaves in the same job
rsandell updated JENKINS-15888 Executing different build steps on different slaves in the same job Not an issue for the multi-slave-config plugin Change By: rsandell (21/Nov/12 10:03 AM) Component/s: core Component/s: multi-slave-config 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-15864) multi-configuration project ignores slave setting
rsandell assigned JENKINS-15864 to Unassigned multi-configuration project ignores slave setting Nothing to do with the multi-slave-config plugin. Change By: rsandell (19/Nov/12 2:19 PM) Assignee: rsandell 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-15864) multi-configuration project ignores slave setting
rsandell updated JENKINS-15864 multi-configuration project ignores slave setting Change By: rsandell (19/Nov/12 2:18 PM) Component/s: multi-slave-config 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-15569) draft-published trigger doesn't work
rsandell assigned JENKINS-15569 to David Pursehouse draft-published trigger doesn't work Change By: rsandell (22/Oct/12 8:31 AM) Assignee: rsandell David Pursehouse 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-15313) Trigger on Updated Change does not fetch the last commit
rsandell commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit Change Merged is a "change based" event so I think that the refspec should be there, it is only the ref updated that is special. So I think that the two last jobs could be merged into one. But I haven't tested it my self 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-15313) Trigger on Updated Change does not fetch the last commit
rsandell commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit The refUpdated event that gerrit sends does not contain a ref spec, since it is not tied to a change. So there is no parameter added to the build named GERRIT_REFSPEC when it is triggered bu a ref updated event. This makes it hard to easily configure a job to trigger on both "change based" events and ref updated events. unless you use a bash script or something to check out the code. I missed to add that to the help text. 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-15264) 'Build Current Patches Only' clears entire queue
rsandell commented on JENKINS-15264 'Build Current Patches Only' clears entire queue This is how it works in our test bed when we have been testing it: Change 10 patchset 1 is uploaded and Jenkins starts build #2 a short while later change 10 patchset 2 is uploaded and Jenkins aborts build #2 and starts build #3 change 11 patchset 1 is uploaded and Jenkins starts build #4 (not cancelling build #3 since it belongs to a different change) Is it the same behavior that you see? 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-15264) 'Build Current Patches Only' clears entire queue
rsandell commented on JENKINS-15264 'Build Current Patches Only' clears entire queue The intention of it is to cancel all builds of a change when a new patchset of the change is uploaded, it is not tied to a specific uploader but the change. 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-6866) Branch type select boxes not visible in internet explorer
rsandell resolved JENKINS-6866 as Won't Fix Branch type select boxes not visible in internet explorer Nobody should use IE6 anymore. Change By: rsandell (20/Sep/12 10:27 AM) Status: Open Resolved Resolution: Won't Fix 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-7067) Try to connect to gerrit using default values without administrator's agreement
rsandell resolved JENKINS-7067 as Fixed Try to connect to gerrit using default values without administrator's agreement Released in 2.3.1 Change By: rsandell (20/Sep/12 9:20 AM) Status: Open Resolved 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
[JIRA] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
rsandell commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit A couple of different fixes around this area has been done up to (including) version 2.6.0 Can you see if those fixes has resolved this one as well? 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-10224) Gerrit plugin doesn't work in current Jenknis version
rsandell commented on JENKINS-10224 Gerrit plugin doesn't work in current Jenknis version What version? Is it still an 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-8341) Failed to serialize GerritManualCause
rsandell resolved JENKINS-8341 as Fixed Failed to serialize GerritManualCause I think it was 2.5.1 :$ Change By: rsandell (20/Sep/12 9:08 AM) Status: Open Resolved 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
[JIRA] (JENKINS-10055) NullPointerException when manually triggering build
rsandell commented on JENKINS-10055 NullPointerException when manually triggering build Released in 2.6.0 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-11726) NOT_BUILT should not considered a failure
rsandell resolved JENKINS-11726 as Fixed NOT_BUILT should not considered a failure Released in 2.6.0 Change By: rsandell (20/Sep/12 9:06 AM) Status: Open Resolved 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
[JIRA] (JENKINS-13004) Remove the nonsense configurations in multi-configuration project
rsandell assigned JENKINS-13004 to Unassigned Remove the nonsense configurations in multi-configuration project Change By: rsandell (13/Aug/12 10:49 AM) Assignee: rsandell 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-13004) Remove the nonsense configurations in multi-configuration project
rsandell commented on JENKINS-13004 Remove the nonsense configurations in multi-configuration project Since it was originally put on a component that I owned this issue was assigned to me, even though I removed the component I guess that noone has taken it since I am assigned to it. I'll try to unassign myself again and hope that someone else picks it up. 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-12646) API returns previous builds status
rsandell assigned JENKINS-12646 to Unassigned API returns previous builds status Change By: rsandell (12/Jul/12 1:03 PM) Assignee: rsandell 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-12646) API returns previous builds status
rsandell updated JENKINS-12646 API returns previous builds status Change By: rsandell (12/Jul/12 1:03 PM) Component/s: multi-slave-config 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-14409) RuntimeException in RunListeners may cause Future.get to never return
rsandell created JENKINS-14409 RuntimeException in RunListeners may cause Future.get to never return Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Jul/12 1:00 PM Description: For example the parameterized-trigger uses Future.get to wait for a triggered build to finish, when a NullpointerException was thrown in the ArtifactDeployer's onDeleted the build that waited was waiting forever. The exception from the log that caused Future.set to not be called correctly was: Jul 5, 2012 11:00:24 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$DeleteRemoteArtifact.onDeleted(ArtifactDeployerPublisher.java:187) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$DeleteRemoteArtifact.onDeleted(ArtifactDeployerPublisher.java:171) at hudson.model.listeners.RunListener.fireDeleted(RunListener.java:208) at hudson.model.Run.delete(Run.java:1187) at hudson.model.AbstractBuild.delete(AbstractBuild.java:362) at hudson.tasks.LogRotator.perform(LogRotator.java:157) at hudson.model.Job.logRotate(Job.java:315) at hudson.model.Run.run(Run.java:1440) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:175) Although it was due to an exception in a plugin I think the Executor should be a bit more robust in this case. This mail thread has a similar description of the problem: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/P7XiYknqgoI Environment: Jenkins 1.424.2 Jenkins 1.447.2 Project: Jenkins Priority: Minor Reporter: rsandell 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-14289) Multi-configuration project chooses wrong slave to build the project
rsandell updated JENKINS-14289 Multi-configuration project chooses wrong slave to build the project wrong component Change By: rsandell (03/Jul/12 9:08 AM) Component/s: core Component/s: multi-slave-config 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-14289) Multi-configuration project chooses wrong slave to build the project
rsandell assigned JENKINS-14289 to Unassigned Multi-configuration project chooses wrong slave to build the project Change By: rsandell (03/Jul/12 9:09 AM) Assignee: rsandell 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-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
rsandell created JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 02/Jul/12 2:02 PM Description: Started by upstream project "Experimental_bobby_MatrixParameterized" build number 2 Building on master [nisse] $ /bin/sh -xe /srv/hudson/tomcat/latest/temp/hudson5741840414633660975.sh + echo another FATAL: Can't parse test2 java.lang.IllegalArgumentException: Can't parse test2 at hudson.matrix.Combination.fromString(Combination.java:218) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:442) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:91) at jenkins.model.Jenkins.getItem(Jenkins.java:2142) at jenkins.model.Jenkins.getItem(Jenkins.java:2163) at hudson.model.Items.fromNameList(Items.java:100) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getProjectList(BuildTriggerConfig.java:132) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:241) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:56) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:96) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:697) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467) at hudson.model.Run.run(Run.java:1404) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Environment: Plugin version 2.15 Jenkins ver. 1.447.2 Project: Jenkins Priority: Critical Reporter: rsandell 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-8226) Add reviewers in gerrit when a build is successful
rsandell commented on JENKINS-8226 Add reviewers in gerrit when a build is successful Since I don't have time to implement it I could give some hints ToGerritRunListener is the central hub for coordinating when builds starts and completes. when all builds for a GerritEvent are completed then NotificationFactory.queueBuildCompleted will be called that will add a BuildCompletedCommandJob to a processing queue for outgoing Gerrit commands. When it is processed it will calculate the final score(s) to send with the help of some other utility classes. So you could either create a new CommandJob type that gathers the list of reviewers depending on the outcome from all builds and sends a set-reviewers command. Or add to the BuildCompletedcommandJob to also send a set-reviewers command. I don't know which approach would be best, I think I would prefer the first alternative, but it could be a bit complex to realize compared to adding to the previous command since it has already done most of the calculations needed. The configuration would be quite straight forward; the Config class holds the central configuration for how the commands themselves should look and the GerritTrigger class holds the configuration for each job. Just send me a mail if you have any questions! /B 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-13117) Allow triggering on the change-merged event too
[
https://issues.jenkins-ci.org/browse/JENKINS-13117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160392#comment-160392
]
rsandell commented on JENKINS-13117:
https://github.com/jenkinsci/gerrit-trigger-plugin/pull/9
> Allow triggering on the change-merged event too
> ---
>
> Key: JENKINS-13117
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13117
> Project: Jenkins
> Issue Type: Improvement
> Components: gerrit-trigger
>Reporter: R. Tyler Croy
>Assignee: rsandell
>
> Gerrit will fire a {{change-merged}} event when a change is "Submitted" (i.e.
> merged) into the destination branch.
> It would be most useful to be able to allow a job to be triggered off of the
> usual {{patchset-created}} event (existing behavior), as well as the
> {{change-merged}} event.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13004) Remove the nonsense configurations in multi-configuration project
[ https://issues.jenkins-ci.org/browse/JENKINS-13004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rsandell updated JENKINS-13004: --- Component/s: core (was: multi-slave-config) Moving the issue to core since it has nothing to do with the multi-slave-config plugin. > Remove the nonsense configurations in multi-configuration project > - > > Key: JENKINS-13004 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13004 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Windows, Mac >Reporter: Michael Lin >Assignee: rsandell > Labels: multi-configuration > > I use Jenkins to configure my multi-configuration project. > The Axes I use are: > Labels: Mac10.6, Mac10.7, and Windows > Platforms: Mac10.6, Mac10.7, WinXP, Win7, and WinServer2008 > Tasks: _App_Installer_, _App_Uninstaller_, and so on > A matrix will be generated, and I intend to let the tasks from windows > platforms go to execute on Windows machines(with Label "Windows"), by using a > filter as > (label=="Windows"&&(Platforms=="Win7"||Platforms=="WinXP"||Platforms=="WinServer2008")). > The matrix will be setup and the unconfigured nodes are gray out, however, it > is clear that it makes no sense for the node "WinXP" to exist on label > Mac10.6 and etc. Although it is shown as diabled/unconfigured/gray, I would > prefer you can provide a choice to remove them from the UI. > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12824) Master does not build due to version bump
[ https://issues.jenkins-ci.org/browse/JENKINS-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159220#comment-159220 ] rsandell commented on JENKINS-12824: Oh yes, I always forget that. :$ > Master does not build due to version bump > - > > Key: JENKINS-12824 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12824 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger >Reporter: James Blair >Assignee: rsandell > > The recent version bump to build-config 1.2.5-SNAPSHOT is incomplete, so > master doesn't currently build. > The build-config dependency versions in the other subprojects need to be > updated to match. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11582) Allow subsequent patchsets to cancel running/pending builds triggered for a change
[ https://issues.jenkins-ci.org/browse/JENKINS-11582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159214#comment-159214 ] rsandell commented on JENKINS-11582: Experimental fix released in Gerrit Trigger 2.4.0, but it is not working fully as intended, JENKINS-12152 could have something to do with it. But I need help in debugging this. > Allow subsequent patchsets to cancel running/pending builds triggered for a > change > -- > > Key: JENKINS-11582 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11582 > Project: Jenkins > Issue Type: Improvement > Components: gerrit-trigger >Reporter: R. Tyler Croy >Assignee: rsandell > > Our tests are long running which means we might have a 15-20 minute > turn-around on pre-testing commits in Gerrit. > In the cases where a developer quickly realizes their error, and submits a > patchset 2, while a patchset 1 is already running wastes a *lot* of Jenkins > slave resources. > Ideally when I upload Change 13, patchset 2, all pending or running jobs > triggered off of Change 13, patchset 1, should be cancelled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11009) Trigger monitor panel of gerrit manual trigger fails to show jobs triggered when job is silent mode (does show selected patches).
[ https://issues.jenkins-ci.org/browse/JENKINS-11009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rsandell closed JENKINS-11009. -- Resolution: Fixed Released in Gerrit Trigger version 2.4.0 > Trigger monitor panel of gerrit manual trigger fails to show jobs triggered > when job is silent mode (does show selected patches). > -- > > Key: JENKINS-11009 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11009 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger >Affects Versions: current >Reporter: stephen ware >Assignee: rsandell >Priority: Minor > Attachments: > 0001-Move-the-checks-for-silent-mode-to-only-wrap-the-cal.patch > > > Select a patch and trigger it. > Patch icon shows up in monitor panel but panel does not detect that a job was > triggered. > Go to specific job/build page and job shows that it was triggered manually. > I'll have a fix suggestion for your perusal soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
