[JIRA] [build-failure-analyzer] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Evgeny Kryukov reopened JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Jenkins installed as war in tomcat. Image URL - http://myhost:8080/jenkins/jenkins/plugin/build-failure-analyzer/images/16x16/information.png is broken, double "jenkins" in path. Change By: Evgeny Kryukov (04/Apr/13 7:14 AM) Resolution: Fixed Status: Resolved Reopened 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] [master-slave] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
Daniel Petisme commented on JENKINS-10771 hudson.util.IOException2: remote file operation failed Same issue: Version: Jenkins 1.424.2 Master: Suse Enterprise Linux Enterprise 10 SP2 Slave: Windows XP SP2 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] [drmemory] (JENKINS-17464) Invisible Graph list (our case 8914)
Mads Nielsen created JENKINS-17464 Invisible Graph list (our case 8914) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: drmemory Created: 04/Apr/13 8:07 AM Description: The list containing the available graphs is invisible until you save the job and reconfigure. Project: Jenkins Priority: Major Reporter: Mads Nielsen 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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
herve_colliaux commented on JENKINS-16533 Jobs checked out from svn with pinned externals continuously run (with no changes in svn) In my case, externals without any fixed revision numbers, it occurs only with the version 1.45 of the plugin. It is back to normal again when I return to the version 1.44. (jenkins 1.509 and subversion 1.6) 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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
Emil Styrke commented on JENKINS-16533 Jobs checked out from svn with pinned externals continuously run (with no changes in svn) Indeed. I have not tried 1.44, but reverting to 1.43 it seems to work again. This is a sufficient workaround for me at the moment. 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] [rtc] (JENKINS-15572) Should be able to customize command line executable per slave node
Royston Shufflebotham assigned JENKINS-15572 to Royston Shufflebotham Should be able to customize command line executable per slave node Change By: Royston Shufflebotham (04/Apr/13 8:33 AM) Assignee: Deluan Quintão Royston Shufflebotham 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] [memory-map] (JENKINS-17465) Missing data from bar chart
Craig Lawton-Devine created JENKINS-17465 Missing data from bar chart Issue Type: Bug Affects Versions: current Assignee: Praqma Support Attachments: memory-map_missing_data.png Components: memory-map Created: 04/Apr/13 8:38 AM Description: When specifying two memory section to display on one chart using comma separation, the bar chart doesn’t display the columns for the latest build. This is evident on the RAM chart on the plugin wiki page: https://wiki.jenkins-ci.org/display/JENKINS/memory+map+plugin#MemoryMapPlugin-Usage In the above example the first build shown is #21 and the last is #38 but the axis has labels for #21 to #39. i.e. the bars for #39 is missing. The attached screenshot from my own job demonstrates the problem more clearly. Builds #1 to #9 are successful and were built with memory-map configured. Builds #1 to #9 are listed on the chart axis, but only 8 red and 8 blue bars are shown, #9 is missing both the .text and .bss sections Environment: Windows 7 Windows Server 2007 Project: Jenkins Priority: Major Reporter: Craig Lawton-Devine 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] [memory-map] (JENKINS-17466) Graph configuration not effective until after another build
Craig Lawton-Devine created JENKINS-17466 Graph configuration not effective until after another build Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: memory-map Created: 04/Apr/13 8:45 AM Description: After changing the memory-map graph configuration for the job, the graphs on the job page and memory map publisher page are not updated. Although the graphs will be updated after a build, it should be possible to view the reconfigured graph without that step. Environment: Windows 7 Windows XP Project: Jenkins Priority: Major Reporter: Craig Lawton-Devine 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] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Vlad Aginsky created JENKINS-17467 CoverityPublisher aborted due to NullPointerException Issue Type: Bug Assignee: Unassigned Components: coverity Created: 04/Apr/13 8:56 AM Description: start getting this after upgade to coverity 1.2.0 00:04:36.725 Connecting to server jena102:9090 00:04:36.909 2013-04-04 08:48:34 UTC - Committing 237 file descriptions... 00:04:36.909 |0-25-5075100| 00:04:37.324 00:04:39.510 2013-04-04 08:48:34 UTC - Calculating 237 cross-references... 00:04:39.510 |0-25-5075100| 00:04:41.284 00:04:41.288 2013-04-04 08:48:38 UTC - Committing 237 cross-references... 00:04:41.289 |0-25-5075100| 00:04:42.098 00:04:44.581 2013-04-04 08:48:41 UTC - Committing 1979 functions... 00:04:44.581 |0-25-5075100| 00:04:44.795 00:04:46.355 2013-04-04 08:48:43 UTC - Committing 55 defect occurrences... 00:04:46.355 |0-25-5075100| 00:04:46.360 00:04:50.226 2013-04-04 08:48:47 UTC - Committing 3 output files... 00:04:50.226 |0-25-5075100| 00:04:50.234 00:04:50.253 New snapshot ID 23853 added. 00:04:50.254 Elapsed time: 00:00:13 00:04:50.255 static done 00:04:50.378 Archiving artifacts 00:04:50.402 ERROR: Publisher jenkins.plugins.coverity.CoverityPublisher aborted due to exception 00:04:50.403 java.lang.NullPointerException 00:04:50.403 at jenkins.plugins.coverity.CoverityPublisher.perform(CoverityPublisher.java:248) 00:04:50.403 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) 00:04:50.403 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) 00:04:50.403 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770) 00:04:50.404 at hudson.model.Build$BuildExecution.post2(Build.java:183) 00:04:50.404 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:720) 00:04:50.404 at hudson.model.Run.execute(Run.java:1600) 00:04:50.404 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 00:04:50.404 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:04:50.405 at hudson.model.Executor.run(Executor.java:237) 00:04:50.406 Email was triggered for: Failure Environment: jenkins 1.509, coverity plugin 1.2.0 Project: Jenkins Priority: Blocker Reporter: Vlad Aginsky 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] [memory-map] (JENKINS-17466) Graph configuration not effective until after another build (our case 8955)
Jens Brejner updated JENKINS-17466 Graph configuration not effective until after another build (our case 8955) Linking to our internal tracker Change By: Jens Brejner (04/Apr/13 9:02 AM) Summary: Graph configuration not effective until after another build (our case 8955) 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] [memory-map] (JENKINS-17465) Missing data from bar chart (our case 8954)
Jens Brejner updated JENKINS-17465 Missing data from bar chart (our case 8954) Linking to our internal tracker Change By: Jens Brejner (04/Apr/13 9:03 AM) Summary: Missing data from bar chart (our case 8954) 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] [core] (JENKINS-15799) loosing matrix sub builds
Zvi Karov reopened JENKINS-15799 loosing matrix sub builds I updated to version 1.508 on Windows 7 /64 bit. In all my matrix, sub build olders than 2 days - removed from disk, the build is not on the disk anymore. parents build not removed. Change By: Zvi Karov (04/Apr/13 9:36 AM) Resolution: Fixed Status: Resolved Reopened 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] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak created JENKINS-17468 NullPointerException in URLTrigger.getFTPResponse during startup Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 04/Apr/13 9:49 AM Description: The trigger mechanism does not seem to work for FTP URLs. I get the following information shown in the URLTrigger log: [URLTrigger] - Poll with a URL Polling started on Apr 4, 2013 9:44:47 AM Polling for the job testjob Looking nodes where the poll can be run. Looking for a node to the restricted label master. Polling on master. Failed to poll URL: java.lang.NullPointerException Skipping URLTrigger initialization. Waiting next schedule Polling complete. Took 8 ms. No changes. I also find the following log messages in the jenkins logs: SEVERE: Severe error on trigger startup null java.lang.NullPointerException at org.jenkinsci.plugins.urltrigger.URLTrigger.getFTPResponse(URLTrigger.java:356) at org.jenkinsci.plugins.urltrigger.URLTrigger.start(URLTrigger.java:299) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:97) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) at hudson.model.AbstractProject.submit(AbstractProject.java:1803) at hudson.matrix.MatrixProject.submit(MatrixProject.java:790) at hudson.model.Job.doConfigSubmit(Job.java:993) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:699) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.d
[JIRA] [core] (JENKINS-15799) loosing matrix sub builds
Zvi Karov edited a comment on JENKINS-15799 loosing matrix sub builds I updated to version 1.508 on Windows 7 /64 bit. In all my matrix, sub build olders than 2 days - removed from disk, the build is not on the disk anymore. parents build not removed. This is the log I got when error occurred first about half an hour after running 1.508 version: Apr 2, 2013 1:42:40 PM hudson.model.RunMap retrieve WARNING: could not load D:\Jenkins\jobs\trunk_st\configurations\axis-Platform\Win\axis-ProjectName\Akado%5CConsumer_Ird\builds\1377 hudson.util.IOException2: Invalid directory name D:\Jenkins\jobs\trunk_st\configurations\axis-Platform\Win\axis-ProjectName\Akado%5CConsumer_Ird\builds\1377 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.matrix.MatrixRun.(MatrixRun.java:58) at sun.reflect.GeneratedConstructorAccessor103.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:1039) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:376) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Caused by: java.text.ParseException: Unparseable date: "1377" at java.text.DateFormat.parse(Unknown Source) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:352) ... 24 more 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] [core] (JENKINS-15799) loosing matrix sub builds
Zvi Karov edited a comment on JENKINS-15799 loosing matrix sub builds I updated to version 1.508 on Windows 7 /64 bit. In all my matrix, sub build olders than 2 days - removed from disk, the sub builds not exists on the disk anymore (so moving back to 1.484 will not restore the old state). parents build were not removed and I see Not run in the status of sub_build in the matrix. This is the log I got when error occurred first about half an hour after running 1.508 version: Apr 2, 2013 1:42:40 PM hudson.model.RunMap retrieve WARNING: could not load D:\Jenkins\jobs\trunk_st\configurations\axis-Platform\Win\axis-ProjectName\Akado%5CConsumer_Ird\builds\1377 hudson.util.IOException2: Invalid directory name D:\Jenkins\jobs\trunk_st\configurations\axis-Platform\Win\axis-ProjectName\Akado%5CConsumer_Ird\builds\1377 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.matrix.MatrixRun.(MatrixRun.java:58) at sun.reflect.GeneratedConstructorAccessor103.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:1039) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:376) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Caused by: java.text.ParseException: Unparseable date: "1377" at java.text.DateFormat.parse(Unknown Source) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:352) ... 24 more 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] [android-emulator] (JENKINS-17435) FATAL: channel is already closed on Android Emulator launch
Christopher Orr closed JENKINS-17435 as Not A Defect FATAL: channel is already closed on Android Emulator launch Change By: Christopher Orr (04/Apr/13 11:30 AM) 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] [external-resource-dispatcher] (JENKINS-17469) The External Resources Manager should handle the state changes of the ExternalResource object
Patrik Johansson started work on JENKINS-17469 The External Resources Manager should handle the state changes of the ExternalResource object Change By: Patrik Johansson (04/Apr/13 12:25 PM) Status: Open In Progress 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] [core] (JENKINS-15799) loosing matrix sub builds
Zvi Karov edited a comment on JENKINS-15799 loosing matrix sub builds I updated to version 1.508 on Windows 7 /64 bit. In all my matrix, sub build olders than 2 days - removed from disk, the sub builds not exists on the disk anymore (so moving back to 1.484 will not restore the old state). parents build were not removed and I see Not run in the status of sub_build in the matrix. parents builds: Symlinks, only for new builds that run with 1.508, but older builds were not removed from history. There are symlinks, but only for the sub builds from last 2 days, all other sub builds - removed from disk and from history of jenkins, and of course no symlink for them. This is the log I got when error occurred first about half an hour after running 1.508 version: Apr 2, 2013 1:42:40 PM hudson.model.RunMap retrieve WARNING: could not load D:\Jenkins\jobs\trunk_st\configurations\axis-Platform\Win\axis-ProjectName\Akado%5CConsumer_Ird\builds\1377 hudson.util.IOException2: Invalid directory name D:\Jenkins\jobs\trunk_st\configurations\axis-Platform\Win\axis-ProjectName\Akado%5CConsumer_Ird\builds\1377 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.matrix.MatrixRun.(MatrixRun.java:58) at sun.reflect.GeneratedConstructorAccessor103.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:1039) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:376) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Caused by: java.text.ParseException: Unparseable date: "1377" at java.text.DateFormat.parse(Unknown Source) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:352) ... 24 more 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=jesperjensen";
style="color:#355564;">Jesper Jensen
edited a comment on https://issues.jenkins-ci.org/images/icons/bug.gif"; height="16" width="16"
border="0" align="absmiddle" alt="Bug"> JENKINS-9321
Discard old
data ends in a NullPointerException
Also in 1.508
Stack trace:
Status Code: 500
Exception: java.lang.NullPointerException
Stacktrace:
javax.servlet.ServletException: java.lang.NullPointerException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at
winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?avatarId=10275"; alt=""
height="48" width="48" border="0" align="left" style="padding:0;margin: 0 16px
16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=jesperjensen";
style="color:#355564;">Jesper Jensen
commented on https://issues.jenkins-ci.org/images/icons/bug.gif";
height="16" width="16" border="0" align="absmiddle" alt="Bug"> JENKINS-9321
Discard old
data ends in a NullPointerException
Also in 1.508
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] [subversion] (JENKINS-16854) svn:externals with fixed revision causes continuous builds
kutzi resolved JENKINS-16854 as Duplicate svn:externals with fixed revision causes continuous builds Change By: kutzi (04/Apr/13 1:20 PM) Status: Open Resolved Resolution: Duplicate 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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
kutzi commented on JENKINS-16533 Jobs checked out from svn with pinned externals continuously run (with no changes in svn) So there are contradicting reports here. The reporter says that it is broken with 1.44 - Herve says that it is broken with 1.45 and and is fixed when going back to 1.44. BTW: a test job would certainly help to get this 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] [subversion] (JENKINS-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
kutzi assigned JENKINS-16533 to Tom Palmer Jobs checked out from svn with pinned externals continuously run (with no changes in svn) Maybe related to https://github.com/jenkinsci/subversion-plugin/commit/1e685c2e58160f8353d52ba92a6066a39f107443 therefore assigning to you, Tom. Change By: kutzi (04/Apr/13 1:32 PM) Assignee: Tom Palmer 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] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Jeffrey Damick commented on JENKINS-17386 Gradle.properties ignored after 1.22 upgrade +1 also a problem for us, global properties & nexus creds were in $HOME/.gradle, had to revert to 1.21 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] [cvs] (JENKINS-17470) uncheck "Show all CVS Output" has no effect
Nicolas De Loof created JENKINS-17470 uncheck "Show all CVS Output" has no effect Issue Type: Bug Assignee: Unassigned Components: cvs Created: 04/Apr/13 2:36 PM Description: running command line cvs with -Q option just make it quiet during checkout configuring jenkins cvs plugin with "Show all CVS Output", that configures cvsclient library to run with globalOptions#ceryQuiet has no effect. I've double checked with a debugger -Q option is well added to the request, but server still sends messages on stderr to Listener. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof 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] [core] (JENKINS-17471) Maven Buildstep and Maven project are completely different
Marc Günther created JENKINS-17471 Maven Buildstep and Maven project are completely different Issue Type: Bug Assignee: Unassigned Components: core, maven Created: 04/Apr/13 3:07 PM Description: The configuration of a "Invoke top-level Maven targets" build step in a Freestyle project, and the configuration of the Build section in a Maven project type are so completely different, that I don't even know where to begin. Options are called differently, are in a different order, some are missing from the first, some are missing from the other. Imho, these should really be completely the same. Missing on one side: Properties: this nice textarea is missing completely from the maven project type, instead we have to use -D... in a single-line textfield Use private Maven repository: the freestyle version is missing the "local to executor" option Run headless: only available in Maven project Maven Validation level: ditto Naming inconsistencies: JVM Options <-> MAVEN_OPTS: same thing, different names, also MAVEN_OPTS might sound to the unwary that you can put your properties here "Goals" <-> "Goals and options": also it's an expandable textbox in Freestyle, but not in Maven project Different order/section: "Goals" and "Pom" fields are swapped "Use custom workspace": Freestyle: hidden in "Advanced project options", maven: in main Build section "Build Environment": Freestyle: above the Build section, Maven: below the Build section There are some more options in Maven project, that only make sense there, so that's OK. But at least the rest should be identical. Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Marc Günther updated JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Change By: Marc Günther (04/Apr/13 3:08 PM) Priority: Major Minor 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] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
Jesse Glick commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Resolved only if and when PR accepted. 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] [core] (JENKINS-10407) builds/1234, lastSuccessful and lastStable symlinks not created
jaffy joffa commented on JENKINS-10407 builds/1234, lastSuccessful and lastStable symlinks not created Im seeing the same issue in 1.508 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] [git] (JENKINS-10385) FATAL: Could not checkout null with start point after a reset --hard to remove a commit
eguess74 reopened JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit We just hit this problem with one of the jobs. The scenario was that the faulty commit was pushed to the repo, it was built in Jenkins, then it was reset --hard to previous commit and force pushed. After that the workspace was wiped out and now I can't build the job because it complains that it can't find the last built revision which it tries to start with. Jenkins 1.509, git plugin 1.1.23 Change By: eguess74 (04/Apr/13 3:50 PM) Resolution: Fixed Status: Resolved Reopened 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] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick assigned JENKINS-10524 to Jesse Glick winstone.ClientSocketException: Failed to write to client Change By: Jesse Glick (04/Apr/13 3:52 PM) Assignee: Jesse Glick 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] [xvnc] (JENKINS-16879) More robust display detection needed - builds fail when many builds require Xvnc
Levon Saldamli resolved JENKINS-16879 as Fixed More robust display detection needed - builds fail when many builds require Xvnc Resolved in xvnc-1.12 Change By: Levon Saldamli (04/Apr/13 3:55 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] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Levon Saldamli commented on JENKINS-17280 Display number out of bounds, no way to reset 1) is implemented now in xvnc-1.12, but not 2) Is this sufficient to resolve this bug? 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] [ec2] (JENKINS-17410) Unable to delete ec2 slave
John Dyer commented on JENKINS-17410 Unable to delete ec2 slave I am using the Jenkins EC2 plugin Is there another that works better which I should be using instead? 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] [configurationslicing] (JENKINS-17472) NPE in function "Delete workspace before build starts"
Walter Kacynski created JENKINS-17472 NPE in function "Delete workspace before build starts" Issue Type: Bug Assignee: mdonohue Components: configurationslicing Created: 04/Apr/13 4:10 PM Description: When using the function "Delete workspace before build starts" An error 500 is returning using Jenkins 1.502 and configuration slicing 1.36 Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFil
[JIRA] [configurationslicing] (JENKINS-14456) Add support for Workspace Cleanup Plugin
Walter Kacynski commented on JENKINS-14456 Add support for Workspace Cleanup Plugin New JIRA for reported bug: JENKINS-17472 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] [git] (JENKINS-10385) FATAL: Could not checkout null with start point after a reset --hard to remove a commit
eguess74 commented on JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit It seems that last built revision is retained in Jenkins memory and there is no way to force git plugin to forget it in this particular scenario other then restart the whole server or delete and recreate the project. May be we could have a link in GUI (somewhere under git polling log) allowing to reset last built revision together with performing a reset --hard on the repo where all local branches will be reset to their remote counterparts state? 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] [parameterized-trigger] (JENKINS-17473) parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued
Walter Stone created JENKINS-17473 parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 04/Apr/13 4:32 PM Project: Jenkins Priority: Major Reporter: Walter Stone 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] [core] (JENKINS-17474) clicking Apply when renaming a project fails
Marc Günther created JENKINS-17474 clicking Apply when renaming a project fails Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Apr/13 4:44 PM Description: In the Configure page of a Job: change the name click Apply instead of Save You will get a big empty draggable box with the title "Error" Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer created JENKINS-17475 Backup stops when processing some file like 'latestfailedbuild' Issue Type: Bug Assignee: Thomas Fürer Components: thinBackup Created: 04/Apr/13 4:46 PM Description: 03.04.2013 09:13:04 org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SCHWERWIEGEND: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'C:\CIServer\Backup\'. java.io.IOException: Source 'C:\Program Files (x86)\Jenkins\jobs\Bank Trunk\builds\lastFailedBuild' exists but is not a directory at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:869) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:302) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:270) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:208) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:196) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:175) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:142) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Unknown Source) 03.04.2013 09:12:40 org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 63 jobs to back up. 03.04.2013 09:12:40 org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doBackupManual INFO: Starting manual backup. Indeed, lastFailedBuild is a normal file and not a directory. Since Jenkins 1.507 there are these special files (see http://jenkins-ci.org/changelog). Do you think you can address this issue quickly? Environment: Jenkins since 1.507 (reproduced on 1.509) thinBackup 1.7.2 Project: Jenkins Priority: Blocker Reporter: Thomas Fürer 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] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Jesse Glick assigned JENKINS-17280 to Levon Saldamli Display number out of bounds, no way to reset Change By: Jesse Glick (04/Apr/13 4:50 PM) Assignee: Jesse Glick Levon Saldamli 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] [parameterized-trigger] (JENKINS-17476) parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated
Walter Stone created JENKINS-17476 parameterized-trigger List Subversion tags default value set to a current build parameter not evaluated Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 04/Apr/13 4:55 PM Description: When triggering a downstream build project using current build parameters a defined string parameter in the upstream triggering project is not evaluated if entered into the list subversion tags default of the downstream project. The intent is to have a subversion tag specified in an upstream project used in downstream projects to setup the workspace. This arrangement is intended to allow the upstream project to define the svn tag for all downstream projects and still allow the dowmstream projects to be executed directly without any reconfiguration. Environment: Windows, Linux Project: Jenkins Priority: Major Reporter: Walter Stone 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] [parameterized-trigger] (JENKINS-17473) parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued
Walter Stone commented on JENKINS-17473 parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued This Jira is a failed attempt to create a JIra, PLEASE CLOSE 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] [parameterized-trigger] (JENKINS-17473) parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued
Walter Stone resolved JENKINS-17473 as Incomplete parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued Change By: Walter Stone (04/Apr/13 5:00 PM) Status: Open Resolved 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 -- 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] [parameterized-trigger] (JENKINS-17473) parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued
Walter Stone closed JENKINS-17473 as Incomplete parameterized-trigger List Subversion Tags Default value specifying current parameter not evalued failed create Jira Change By: Walter Stone (04/Apr/13 5:02 PM) Status: Resolved Closed Assignee: huybrechts Walter Stone 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] [active-directory] (JENKINS-17477) Active Directory plugin not working with SSL connections
David Ishee created JENKINS-17477 Active Directory plugin not working with SSL connections Issue Type: Bug Assignee: Unassigned Components: active-directory Created: 04/Apr/13 5:07 PM Description: Can't connect to Active Directory from a Linux machine with the Active Directory plugin. Our servers require SSL access, no anonymous binds. Simple authentication over SSL is OK. I've supplied the: -Djavax.net.ssl.trustStore=/path/to/jenkins/truststore.crt and -Djavax.net.ssl.trustStorePassword=mypass arguments to Jenkins on startup. The Active Directory plugin v1.17 on Hudson works. Apr 4, 2013 11:45:29 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm FINE: Connecting to ldap://hostname:3269/ Apr 4, 2013 11:45:30 AM hudson.plugins.active_directory.TrustAllSocketFactory FINE: Got the certificate: [[ (output looks OK here) ]] Apr 4, 2013 11:45:30 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm FINE: Failed to start TLS. Authentication will be done via plain-text LDAP javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090DF2, comment: TLS or SSL already in effect, data 0, v1db1]; remaining name '' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3081) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2987) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2794) at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3166) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DesciprotrImpl.bind(ActiveDirectorySecurityRealm.java:413) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DesciprotrImpl.bind(ActiveDirectorySecurityRealm.java:357) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:245) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:190) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:134) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:71) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDisp
[JIRA] [core] (JENKINS-17110) Hover-over "Build Now" broken for parameterized jobs: "This page expects a form submission"
Jesse Glick assigned JENKINS-17110 to Jesse Glick Hover-over "Build Now" broken for parameterized jobs: "This page expects a form submission" Change By: Jesse Glick (04/Apr/13 5:22 PM) Assignee: Jesse Glick 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] [junit] (JENKINS-17478) Add extension point to rewrite test names
Donny Nadolny created JENKINS-17478 Add extension point to rewrite test names Issue Type: Improvement Assignee: Donny Nadolny Components: junit Created: 04/Apr/13 5:26 PM Description: It's easy to write JUnit tests in scala, however scala allows more flexibility in naming than java does. In particular, if you enclose an identifier with back ticks, you can include symbols, spaces, and other characters that are not valid names in java. The scala compiler encodes them, eg `hello world` becomes "hello$u0020world". It can be helpful to write test method names between back ticks so that you can give an easy to read statement of what is the test expects. The problem is that these names are displayed in Jenkins as the encoded version, which is hard to read. This task is to create an extension point to allow a plugin to rewrite the package/class/method names so that they are displayed in the JUnit results pages in a readable format. I've used scala as an example, but this would apply to any JVM language that allows invalid java identifiers in its own identifiers by encoding them. Project: Jenkins Priority: Minor Reporter: Donny Nadolny 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] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
Artur Szostak created JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: urlscm Created: 04/Apr/13 5:40 PM Description: The URL SCM always triggers a build when using the SCP polling option. The Polling Log only contains the following: Started on Apr 4, 2013 5:32:41 PM Done. Took 1 ms Changes found Thus the URL seems to always be marked by the URL plugin as changed, even when no changes have been made. Environment: Scientific Linux 5.5 Architecture x86_64 Running Jenkins in standalone mode with Winstone Project: Jenkins Priority: Major Reporter: Artur Szostak 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] [xvnc] (JENKINS-17280) Display number out of bounds, no way to reset
Alex Vesely commented on JENKINS-17280 Display number out of bounds, no way to reset Jesse Glick wrote: "...automatically clears the blacklist if all ports are either blacklisted or currently allocated." Is this implemented? If so, the issue can be closed, thank you. 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] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
mdonohue commented on JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option URLSCM checks the last-modified time returned by the web server. If the web server always returns a different last-modified time, then you will see the behavior described. 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.
Jenkins 1.509 cannot load build history under weblogic v12.1.1
I have read the posts and added the weblogic.xml to the WEB-INF folder and deployed Jenkins to WebLogic. Everything works fine, except Jenkins gets an error when trying to read the build history from disk. I have verified that the files exist, that I can access them from Jenkins and that they are valid XML format. I have also tried uninstalling all of my plugins. I cannot figure out why Jenkins fails. Has anyone encountered this before? Thanks in advance, Paul Apr 4, 2013 10:34:42 AM hudson.model.RunMap retrieveWARNING: could not load /apps/Oracle/Middleware/user_projects/domains/eja_domain/jenkin_builds/75hudson.util.IOException2: Unable to read /apps/Oracle/Middleware/user_projects/domains/eja_domain/jenkin_builds/2013-04-03_16-08-07/build.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.model.Run.reload(Run.java:311) at hudson.model.Run.(Run.java:297) at hudson.model.AbstractBuild.(AbstractBuild.java:169) at hudson.model.Build.(Build.java:104) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:42)at sun.reflect.GeneratedConstructorAccessor249.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1117) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59)at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:369) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1054) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:140) at hudson.model.Job.getLastFailedBuild(Job.java:853) at sun.reflect.GeneratedMethodAccessor530.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:106) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:82) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:162) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:100) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:106) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:162) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:100) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStati
[JIRA] [core] (JENKINS-17480) Copying a job should disable the copy
Marc Günther created JENKINS-17480 Copying a job should disable the copy Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Apr/13 5:53 PM Description: When i create a new job by using "Copy existing job", the copy is active and can potentially run, while I'm still busy changing it on the Configure page. That can cause unwanted effects, for example if that job manipulates external resources, which will now happen twice. Expected: The copy should be disabled till I first save it from the configuration screen. Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
Artur Szostak commented on JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option This happens even when I use HTTP URLs to Jenkins' workspaces, HTTP URLs for lighttpd or FTP URLs for vsftpd. Thats 3 different servers. Seems unlikely that its due to the server. Can you suggest a conclusive way to check? 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer started work on JENKINS-17475 Backup stops when processing some file like 'latestfailedbuild' Change By: Thomas Fürer (04/Apr/13 6:26 PM) Status: Open In Progress 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] [core] (JENKINS-15365) Invalid translation
Harald Albers assigned JENKINS-15365 to Harald Albers Invalid translation Change By: Harald Albers (04/Apr/13 6:36 PM) Assignee: Harald Albers 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer commented on JENKINS-17475 Backup stops when processing some file like 'latestfailedbuild' Integrated in thinBackup #80 JENKINS-17475: add new files in the builds folder to the backup archive (Revision 9dd19dfccf35fb323e9dd34eb7d40ff672f47070) Result = SUCCESS tfuerer.javanet : 9dd19dfccf35fb323e9dd34eb7d40ff672f47070 Files : pom.xml src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/java/org/jvnet/hudson/plugins/thinbackup/restore/PluginRestoreUpdateCenter.java 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] [core] (JENKINS-15365) Invalid translation
Harald Albers started work on JENKINS-15365 Invalid translation Change By: Harald Albers (04/Apr/13 6:45 PM) Status: Open In Progress 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] [hp-application-automation-tools-plugin] (JENKINS-17481) Implement a platform independent plugin
David Ehringer created JENKINS-17481 Implement a platform independent plugin Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 04/Apr/13 7:31 PM Description: Many large organizations have non-Windows based CI and build environments even if they are integrate with HP. Unfortunately, the current implementation of this plugin isn't very easy to use or to integrate into large CI environments given it's dependency on Windows. Please implement a platform independent version. Project: Jenkins Priority: Critical Reporter: David Ehringer 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-16974) Build Now link on MultiJob page doesn't work
David Ishee commented on JENKINS-16974 Build Now link on MultiJob page doesn't work If you make the MultiJob a parameterized job, the "build now" link on the right side of the screen no longer works, and the one on the left side of the screen now works. The broken vs works icons flip-flop based on whether the job is parameterized or not. 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] [role-strategy] (JENKINS-17482) Support folders
Jesse Glick created JENKINS-17482 Support folders Issue Type: Bug Assignee: Jesse Glick Components: role-strategy Created: 04/Apr/13 7:44 PM Description: To support the CloudBees Folders plugin, or other items not at top level, some minor changes need to be made to this plugin. Project: Jenkins Labels: folders Priority: Major Reporter: Jesse Glick 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] [role-strategy] (JENKINS-17482) Support folders
Jesse Glick started work on JENKINS-17482 Support folders Change By: Jesse Glick (04/Apr/13 7:47 PM) Status: Open In Progress 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] [role-strategy] (JENKINS-17482) Support folders
Jesse Glick updated JENKINS-17482 Support folders Change By: Jesse Glick (04/Apr/13 7:47 PM) URL: https://github.com/jenkinsci/role-strategy-plugin/pull/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] [redmine] (JENKINS-15683) let Redmine links point to project on redmine server
Łukasz Jąder commented on JENKINS-15683 let Redmine links point to project on redmine server I've implemented this in pull request https://github.com/jenkinsci/redmine-plugin/pull/4 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] [core] (JENKINS-14067) Polish localization breaks permalink descriptions
Harald Albers assigned JENKINS-14067 to Harald Albers Polish localization breaks permalink descriptions Change By: Harald Albers (04/Apr/13 8:29 PM) Assignee: Harald Albers 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] [build-pipeline] (JENKINS-17483) Skinnable build pipeline
Kohsuke Kawaguchi created JENKINS-17483 Skinnable build pipeline Issue Type: New Feature Assignee: Unassigned Components: build-pipeline Created: 04/Apr/13 8:29 PM Description: Feedback from users: Now that we've made the data model of the build pipeline plugin pluggable, it'd be nice if the build pipeline would allow make the rendering pluggable — the particular feedback was about showing the same card and arrow like UI but with a different skin (see ThoughtWorks Go Pipeline screenshot for the hint of what he was thinking about.) This seems like a sensible feature as it'd allow other graphically-minded people to innovate. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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] [core] (JENKINS-14067) Polish localization breaks permalink descriptions
Harald Albers started work on JENKINS-14067 Polish localization breaks permalink descriptions Change By: Harald Albers (04/Apr/13 8:29 PM) Status: Open In Progress 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] [core] (JENKINS-10891) Page Title French Translation missing for "New Job" page
Harald Albers assigned JENKINS-10891 to Harald Albers Page Title French Translation missing for "New Job" page Change By: Harald Albers (04/Apr/13 8:57 PM) Assignee: Harald Albers 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] [core] (JENKINS-10891) Page Title French Translation missing for "New Job" page
Harald Albers started work on JENKINS-10891 Page Title French Translation missing for "New Job" page Change By: Harald Albers (04/Apr/13 8:57 PM) Status: Open In Progress 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] [core] (JENKINS-17484) jelly null pointer
Kanstantsin Shautsou created JENKINS-17484 jelly null pointer Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Apr/13 8:59 PM Description: opened main page as anonymous, clicked on view tab that has job that is viewable for anonymous. Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/hudson/model/View/index.jelly:44:43: Cannot invoke method isEmpty() on null object Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/hudson/model/View/index.jelly:44:43: Cannot invoke method isEmpty() on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.staple
[JIRA] [core] (JENKINS-17484) jelly null pointer
Kanstantsin Shautsou updated JENKINS-17484 jelly null pointer Change By: Kanstantsin Shautsou (04/Apr/13 9:08 PM) Environment: lts , jenkins-1.480.3 Description: opened main page as anonymous, clicked on view tab that has job that is viewable for anonymous. Jenkins settings allow anonymous to read "view". Status Code: 500Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/hudson/model/View/index.jelly:44:43: Cannot invoke method isEmpty() on null objectStacktrace:javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.480.3.jar!/hudson/model/View/index.jelly:44:43: Cannot invoke method isEmpty() on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.Compre
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
A K commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Some testing with my own builds shows that the trigger/difference for causing the "java.io.NotSerializableException" is when the advanced setting "Merge before build" is checked off and filled in. Git operations without this seem to work fine. *Haven't tested extensively of course 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] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
A K edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Some testing with my own builds shows that the trigger/difference for causing the "java.io.NotSerializableException" is when the advanced setting "Merge before build" is checked off and filled in. Git operations without this seem to work fine. *Haven't tested extensively of course *Edit: This confirms what David Walend commented on earlier. 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] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
A K commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Additionally, I was able to reproduce this behaviour on OSX and Linux slaves, both 64-bit. 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] [periodicbackup] (JENKINS-13050) No feedback when invalid configuration refuses to save
Marc Brugger updated JENKINS-13050 No feedback when invalid configuration refuses to save Change By: Marc Brugger (04/Apr/13 9:51 PM) Priority: Minor Blocker 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] [periodicbackup] (JENKINS-17485) org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public
Marc Brugger created JENKINS-17485 org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: periodicbackup Created: 04/Apr/13 9:51 PM Description: The org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public. Otherwise extensions of org.jenkinsci.plugins.periodicbackup.FileManager are not possible. Since the abstract method getFilesToBackup() throws this exception it has tu be public. Project: Jenkins Priority: Major Reporter: Marc Brugger 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] [periodicbackup] (JENKINS-17485) org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public
Marc Brugger updated JENKINS-17485 org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public Change By: Marc Brugger (04/Apr/13 9:52 PM) Priority: Major Blocker 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] [periodicbackup] (JENKINS-13050) No feedback when invalid configuration refuses to save
Marc Brugger updated JENKINS-13050 No feedback when invalid configuration refuses to save Change By: Marc Brugger (04/Apr/13 9:52 PM) Priority: Blocker Minor 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] [openid] (JENKINS-17486) Nonce verification failed
Kohsuke Kawaguchi created JENKINS-17486 Nonce verification failed Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: openid Created: 04/Apr/13 10:11 PM Description: If the timestamp of Jenkins master is off, OpenID authentication fails with a cryptic error message of "nonce verification failed". A bit of googling suggests that the incorrect server time setting is the most likely cause of this problem. Given that, the error message shuold improve to suggest that. Or perhaps there can be an administrative monitor to check the timestamp in relation to a time server that the community will run. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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] [tap] (JENKINS-16971) TAP Plug-in not showing TAP contents if it resides in a subdirectory
Dave Goodell commented on JENKINS-16971 TAP Plug-in not showing TAP contents if it resides in a subdirectory This change (https://github.com/jenkinsci/tap-plugin/commit/e8dcf5c) breaks my Jenkins TAP plugin installation. Specifically, the detail links on the http://jenkins.example.org/job/JOBNAME/BUILDNUM/tapTestReport/ page are incorrect. They should read something like http://jenkins.example.org/job/JOBNAME/BUILDNUM/tapTestReport/summary.tap-1/. Instead they read something like http://jenkins.example.org/var/lib/jenkins/jobs/JOBNAME/builds/2013-04-04_12-43-45/tap-master-files/test/mpi/summary.tap-1/. Obviously this URL is invalid and yields an HTTP 404 from the web server. I suspect the problem is caused by the replacement of `getName()` with `getAbsolutePath()`. Reverting commit e8dcf5c fixes the error in my otherwise clean build of 80a01b1. I made no attempt to test or understand the issue actually reported in and/or addressed by this ticket (JENKINS-16971). 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] [periodicbackup] (JENKINS-17487) Allow Excludes in Full Backup
Marc Brugger created JENKINS-17487 Allow Excludes in Full Backup Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: periodicbackup Created: 05/Apr/13 1:26 AM Description: The attached Pattch adds an FileManager which allows to exclude files/dirs by ant exclude pattern. It would be nice if the FileManager could be included to plugin. Regards, bakito Project: Jenkins Priority: Major Reporter: Marc Brugger 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] [periodicbackup] (JENKINS-17485) org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public
Marc Brugger updated JENKINS-17485 org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public Change By: Marc Brugger (05/Apr/13 1:27 AM) Priority: Blocker Major 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] [periodicbackup] (JENKINS-17485) org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public
Marc Brugger commented on JENKINS-17485 org.jenkinsci.plugins.periodicbackup.PeriodicBackupException should be public I extended the main plugin see JENKINS-17487 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] [core] (JENKINS-17265) Builds disappearing from history
Adam Westhusing commented on JENKINS-17265 Builds disappearing from history Thanks for updating the script, but I suppose the behavior is different on Windows. Jenkins has never created symbolic links on Windows until upgrading from 1.506 to 1.509. In the logs, Jenkins is complaining all over the place that it can't find directories but the build directories are actually there and nothing appears to be wrong when bringing up the specific build being complained about in the Jenkins logs. 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] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Nickolay Martinov commented on JENKINS-15355 AdjunctManager: exception upon startup Can see the issue in Jenkins ver. 1.505 Mar 15, 2013 7:49:36 AM org.kohsuke.stapler.jelly.AdjunctTag doTag WARNING: AdjunctManager is not installed for this application. Skipping tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45) 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 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTa
[JIRA] [core] (JENKINS-7488) CLONE -java.io.IOException: Unable to delete - files in dir: []
Nickolay Martinov commented on JENKINS-7488 CLONE -java.io.IOException: Unable to delete - files in dir: [] I can see a bit different stack trace on Jenkins ver. 1.505 Mar 17, 2013 2:06:39 PM hudson.model.Run execute SEVERE: Failed to save build record java.io.IOException: Unable to delete /home/ci/mst/jobs/Infrastructure_free_space_monitoring/configurations/axis-label/ingot/builds/2013-03-17_14-06-01/build.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.XmlFile.write(XmlFile.java:184) at hudson.model.Run.save(Run.java:1702) at hudson.model.Run.execute(Run.java:1623) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) 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] [tap] (JENKINS-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Peter Florijn created JENKINS-17488 java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 05/Apr/13 6:44 AM Description: java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult Project: Jenkins Priority: Major Reporter: Peter Florijn 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] [core] (JENKINS-17265) Builds disappearing from history
Jose Sa commented on JENKINS-17265 Builds disappearing from history You can remove from the script the link sections in Windows environment. But probably in some past upgrade it may have been possible that this same behaviour was accidentally induced in Unix environments which could explain why so many situations similar to that. Still after running the cleanup and running for a few days I don't the problem happening so often now. Actually i saw it happening right in the the first day, but somehow it "recovered" without doing a reload from disk or restart. 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.
