[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Luiko Czub commented on JENKINS-20630 Jenkins fails to start The same here: WinXP SP3, 1.7.0_45, jenkins standalone after switching back to 1.539 jenkins starts works fine again 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] [scm-sync-configuration] (JENKINS-19659) Allow to deactivate bundled scm sync config strategies
Frédéric Camblor updated JENKINS-19659 Allow to deactivate bundled scm sync config strategies Change By: Frédéric Camblor (20/Nov/13 8:14 AM) Description: AfterdiscussiononJENKINS-18187,itappearsitwouldbeanicefeaturetobeingabletodisable[defaultbundledstrategies| i http: / /github.com/jenkinsci/ scm-sync-configuration-plugin/tree/master/src/main/java/hudson/plugins/scm_sync_configuration/strategies/impl]atruntime(onjenkinsglobalconfigpage)Itwouldallowabettertuningofthescm-sync-configbehaviour. 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] [scm-sync-configuration] (JENKINS-19660) Allow to commit SYSTEM-modified files only periodically
Frédéric Camblor commented on JENKINS-19660 Allow to commit SYSTEM-modified files only periodically @clint In your case, I think you could be interested in JENKINS-19659 too Including hudson*.xml files by default is maybe a bad idea as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20666) master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only
hiteswar kumar created JENKINS-20666 master node config not changed from Utilize this slave as much as possible to leave this setting to tied job only Issue Type: Bug Assignee: Unassigned Attachments: master node-issue.jpg Components: core Created: 20/Nov/13 8:29 AM Description: I am trying to change master node config from-"Utilize this slave as much as possible" to-"leave this setting to tied job only" but it is not applied and return back to "Utilize this slave as much as possible" Environment: LTS 1.480.3 Project: Jenkins Priority: Major Reporter: hiteswar kumar 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] [cli] (JENKINS-20667) cli over internet doesn't work
Nick Korotysh created JENKINS-20667 cli over internet doesnt work Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: 2.log Components: cli Created: 20/Nov/13 8:58 AM Description: I posted related bug https://issues.jenkins-ci.org/browse/JENKINS-20128 and was fixed in 1.540. I decided to upgrade both our build servers (1 in our local network and other is remote). When I run (on local jenkins) java -jar jenkins-cli.jar -s http://10.23.0.6:8080/ help --username my_usr --password my_pwd it gives a valid output. When I run (on remote jenkins) java -jar jenkins-cli.jar -s http://us.astorex.com:4555/ help --username my_usr --password my_pwd it crashes. output attached. There are no any issues with version 1.534, reverted to it. Environment: Ubuntu 10.04.4 amd 64, OpenJDK 6 Project: Jenkins Labels: cli, http, internet Priority: Major Reporter: Nick Korotysh 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] [job-restrictions] (JENKINS-20357) Job configuration fails with No page found 'config.jelly' for class com.synopsys.arc.jenkinsci.plugins.jobrestrictions.jobs.UserIdCauseRestriction$DescriptorI
Oleg Nenashev resolved JENKINS-20357 as Fixed Job configuration fails with No page found config.jelly for class com.synopsys.arc.jenkinsci.plugins.jobrestrictions.jobs.UserIdCauseRestriction$DescriptorImpl job-restrictions-2.1 contains a fix for the issue https://github.com/jenkinsci/job-restrictions-plugin/commit/d0a7022355952942732be083f3889b537d21d6c8 Change By: Oleg Nenashev (20/Nov/13 9:09 AM) Status: InProgress 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] [testlink] (JENKINS-20624) TAP result seeker's include test notes adds poor values
Javier Delgado stopped work on JENKINS-20624 TAP result seekers include test notes adds poor values Change By: Javier Delgado (20/Nov/13 9:46 AM) Status: InProgress Open 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-20560) Custom-tools plugin breaks path for android-emulator
Alexander Silgidjian commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator I am experiencing an issue that also seems to be caused by this bug. Once I enable custom tools, I am not able to run Xvnc: Starting xvnc [smoke] $ vncserver :37 /usr/bin/env: perl: No such file or directory Starting xvnc [smoke] $ vncserver :38 /usr/bin/env: perl: No such file or directory Starting xvnc [smoke] $ vncserver :39 /usr/bin/env: perl: No such file or directory Starting xvnc [smoke] $ vncserver :40 /usr/bin/env: perl: No such file or directory FATAL: Failed to run 'vncserver :40' (exit code 127), blacklisting display #40; consider checking the "Clean up before start" option java.io.IOException: Failed to run 'vncserver :40' (exit code 127), blacklisting display #40; consider checking the "Clean up before start" option at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:100) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:73) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) The issue is solved, when I remove custom tool installation from the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-20560) Custom-tools plugin breaks path for android-emulator
Alexander Silgidjian edited a comment on JENKINS-20560 Custom-tools plugin breaks path for android-emulator I am experiencing an issue that also seems to be caused by this bug. Once I enable custom tools, I am not able to run Xvnc: Starting xvnc [smoke] $ vncserver :37 /usr/bin/env: perl: No such file or directory Starting xvnc [smoke] $ vncserver :38 /usr/bin/env: perl: No such file or directory Starting xvnc [smoke] $ vncserver :39 /usr/bin/env: perl: No such file or directory Starting xvnc [smoke] $ vncserver :40 /usr/bin/env: perl: No such file or directory FATAL: Failed to run 'vncserver :40' (exit code 127), blacklisting display #40; consider checking the "Clean up before start" option java.io.IOException: Failed to run 'vncserver :40' (exit code 127), blacklisting display #40; consider checking the "Clean up before start" option at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:100) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:73) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584) at hudson.model.Run.execute(Run.java:1575) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) The issue is solved, when I remove custom tool installation from the job. I am using a snapshot build of custom-tools, because I needed a fix for JENKINS-19506. 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-20481) Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary)
martin naughton commented on JENKINS-20481 Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary) just to clarify you are trying to cancel a build that is successful but just has not finished? So it is a successful build stuck on an executor. Then you press the X button beside the build to stop it. IS this exact test case? 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev
updated JENKINS-20560
Custom-tools plugin breaks path for android-emulator
Change By:
Oleg Nenashev
(20/Nov/13 10:31 AM)
Description:
CreatedfortheoriginalissueinJENKINS-19506{quote}
Iruncustomtools-plugintogetherwithandroid-emulator-plugin,andwhenjenkinslaunchestasksforandroid-emulator,theyarelaunchedwithoutthedefaultPATHvarable.Thismeansthattheshellscriptsthatstarttheemulatorcantfindcommontoolsasdirname,fileandsoon.Workaroundistoaddacustomtoolthatdefinesdefaultpathstoo,butthatssite-wideandwhensomenodeshaveotherPATHsthanother,icanonlyaddthedirectoriesthatexistsonallnodes.
{quote}
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-20481) Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary)
martin naughton commented on JENKINS-20481 Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary) Does it happen all the time? Did you try with java 1.6 to clarify your suspicion? 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev started work on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Change By: Oleg Nenashev (20/Nov/13 10:37 AM) Status: Open InProgress 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] [swarm] (JENKINS-20668) Persist Jenkins swarm slaves when they go offline
Jose Sa created JENKINS-20668 Persist Jenkins swarm slaves when they go offline Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: swarm Created: 20/Nov/13 10:37 AM Description: Whenever there is a problem with a swarm slave that causes its disconnection the slave just disappears. This prevents on first acknowledging there is a problem with that particular slave and secondly finding out more from logs. One possible solution is to have a "sticky" option in slave configuration so to make it persistent in case it goes offline. Another possible solution would be to add in general configuration some time based options for "swarm" specific slaves: connection timeout (ex 15 min) removal timeout (ex: 1 day) The basic idea is the same, to provide more transparency of the status of slaves instead of hiding them when something goes wrong. Project: Jenkins Priority: Major Reporter: Jose Sa 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator I confirm the issue. Hope to resolve it soon 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev updated JENKINS-20560 Custom-tools plugin breaks path for android-emulator Change By: Oleg Nenashev (20/Nov/13 10:42 AM) Environment: custom-tools0.4, Affectedplugins: androidemulatorplugin ,xvncplugin 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-20630) Jenkins fails to start
jagannath behera commented on JENKINS-20630 Jenkins fails to start Having same issue here ..this is my first day with jenkin almost lost whole day with jenkin setup and now this ..Annoying 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1
José Barreto created JENKINS-20669 OrderRetainingMap bug: array index out of range : -1 Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 20/Nov/13 11:14 AM Description: Stack trace javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: -1 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630) at org.kohsuke.stapler.Stapler.service(Stapler.java:224) at javax.servlet.http.HttpServlet.service(HttpServlet.java:723) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:736) Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: -1 at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77) at java.util.HashMap.putAllImpl(HashMap.java:678) at java.util.HashMap.putAll(HashMap.java:669) at com.thoughtworks.xstream.core.util.OrderRetainingMap.init(OrderRetainingMap.java:36) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:135) at
[JIRA] [coverity] (JENKINS-20670) Plugin does not show all defects
André Schramm created JENKINS-20670 Plugin does not show all defects Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: coverity Created: 20/Nov/13 11:31 AM Description: Not all existing defects from the integrity manager are shown, as there is some max limit set (apparently 100 in 1.2.7). Though this seems to improve with commit 7719e16, it to does not seem like a good idea to set some arbitrary number for this without notifying the user or doing so at all - it took me a while to find this. Project: Jenkins Priority: Major Reporter: André Schramm 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1
José Barreto assigned JENKINS-20669 to José Barreto OrderRetainingMap bug: array index out of range : -1 Change By: José Barreto (20/Nov/13 11:33 AM) Assignee: JoséBarreto 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1
José Barreto commented on JENKINS-20669 OrderRetainingMap bug: array index out of range : -1 I use an other solution for running jenkins.war over tomcat: i run a dos command: java -jar jenkins.war And i have my service jenkins running. But i wait a solution when a run it on IBM RAD (eclipse by IBM). Thanks for helps!!! 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-19506) [integration] - android-plugin + custom-tools installation fails due to NPE in ProcStarter::envs()
Oleg Nenashev commented on JENKINS-19506 [integration] - android-plugin + custom-tools installation fails due to NPE in ProcStarter::envs() @Anton https://github.com/jenkinsci/customtools-plugin/pull/13 provides a fix for your initial issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator The draft fix is ready: https://github.com/jenkinsci/customtools-plugin/pull/13 This fix changes order of paths in ProcStarter. It may cause regressions in the case of multiple wrappers exporting same binaries from different folders (not good in any case), but it should work for other cases. 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1
José Barreto edited a comment on JENKINS-20669 OrderRetainingMap bug: array index out of range : -1 I use an other solution for running jenkins.war over tomcat: i run a dos command: java -jar jenkins.war And i have my service jenkins running. But i wait for a solution : normally i run it on IBM RAD (eclipse by IBM). Thanks for helps!!! 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-20630) Jenkins fails to start
Linards L commented on JENKINS-20630 Jenkins fails to start Same here after upgrade from v1.529. 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-client] (JENKINS-20387) Timeout (10min) on git clone command
Oleg Nenashev commented on JENKINS-20387 Timeout (10min) on git clone command Hello, https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin has an implementation of such timeout for external SCM binary calls. https://issues.jenkins-ci.org/browse/JENKINS-15315 describes initial track, but seems that it does not contain all changes... 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-client] (JENKINS-20387) Timeout (10min) on git clone command
Oleg Nenashev edited a comment on JENKINS-20387 Timeout (10min) on git clone command Hello, https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin has an implementation of such timeout for external SCM binary calls. JENKINS-15315 describes initial changes, but seems that it does not contain all commits... 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] [testlink] (JENKINS-20590) New batch build step
Javier Delgado assigned JENKINS-20590 to Javier Delgado New batch build step Change By: Javier Delgado (20/Nov/13 11:51 AM) Assignee: BrunoP.Kinoshita JavierDelgado 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] [testlink] (JENKINS-20590) New batch build step
Javier Delgado started work on JENKINS-20590 New batch build step Change By: Javier Delgado (20/Nov/13 11:51 AM) Status: Open InProgress 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-20560) Custom-tools plugin breaks path for android-emulator
Anton Lundin commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Not that good. Started by user anonymous Building in workspace /home/anton/Downloads/jenkins-dot/workspace/test2 FATAL: Null value not allowed as an environment variable: PATH+ java.lang.IllegalArgumentException: Null value not allowed as an environment variable: PATH+ at hudson.EnvVars.put(EnvVars.java:356) at com.cloudbees.jenkins.plugins.customtools.CustomToolInstallWrapper$2.launch(CustomToolInstallWrapper.java:230) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:420) at hudson.plugins.android_emulator.util.Utils.runAndroidTool(Utils.java:398) at hudson.plugins.android_emulator.SdkInstaller.isPlatformInstalled(SdkInstaller.java:320) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:267) at hudson.plugins.android_emulator.SdkInstaller.installPlatform(SdkInstaller.java:252) at hudson.plugins.android_emulator.SdkInstaller.installDependencies(SdkInstaller.java:239) at hudson.plugins.android_emulator.AndroidEmulator.setUp(AndroidEmulator.java:253) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1679) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) 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] [perforce] (JENKINS-17889) Build one changeset at a time
Jarek Kapica commented on JENKINS-17889 Build one changeset at a time Thanks for suggestion. The pull request: https://github.com/jenkinsci/perforce-plugin/pull/38 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] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
David Caro commented on JENKINS-19470 Build Graph not displaying I'm having the same issue with jenkins 1.537, BuildFlow 0.10, BuildGraphView 1.1.1 and parameterized plugin 2.21, same log also 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Have you got it in the case of empty tools list? 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-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException
jieryn commented on JENKINS-20618 upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException Only 2 occurrences in my log file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException
jieryn commented on JENKINS-20618 upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException Is there a way I can flush cached/compiled jelly on a running Jenkins without restarting the server? 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-20560) Custom-tools plugin breaks path for android-emulator
Anton Lundin commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Yepp. Empty tools list works for non-android-emulator jobs, but it blows up for the android-emulator one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-20560) Custom-tools plugin breaks path for android-emulator
Anton Lundin edited a comment on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Yepp. Empty tools list works for non-android-emulator jobs, but it blows up for the android-emulator one. If i add a tool to the android-emulator job it works as expected. 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-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException
Jesse Glick commented on JENKINS-20618 upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException @jieryn try a System.gc(); JellyClassLoaderTearOff.taglibs is a WeakReference so if this is in fact what keeps compiled Jelly scripts (which I am not sure of), that could work to flush it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Patch has been added to PR. I've added Unit test for this issue, but could you re-test it? Thanks in advance, Oleg 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev edited a comment on JENKINS-20560 Custom-tools plugin breaks path for android-emulator A patch has been added to PR. I've added Unit test for this issue, but could you re-test it? Thanks in advance, Oleg 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] [xunit] (JENKINS-12900) Better feedback needed when a report can't be processed
Marcus Cobden commented on JENKINS-12900 Better feedback needed when a report cant be processed I found that the actual error message ended up in the logs for the build node. 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-client] (JENKINS-20387) Timeout (10min) on git clone command
Mark Waite commented on JENKINS-20387 Timeout (10min) on git clone command Thanks for the pointer, but I don't think the implementation in the Perforce plugin will help. There is already a timeout implementation in the code path used by the Git plugin. I don't understand the code well enough to find the implementation. I assume the message that is displayed is being reported by the joinWithTimeout() method in Jenkins core since it is the only java location in the jenkins, git-plugin, and git-client-plugin directories with the string "Timeout after". Unfortunately, I can't find any callers to that method. I was hopeful that others could find that and provide a pull request for consideration. Alternately, maybe there is a better way to implement the timeout such that it will reset the timeout counter each time data is received from the external process. I thought that was how it was implemented prior to git plugin 2.0, since this problem did not appear until git plugin 2.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-20560) Custom-tools plugin breaks path for android-emulator
Oleg Nenashev commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator Thank you too for the testing, I'll add some tests and release a public version by the weekend. 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] [ldap] (JENKINS-20671) Provide daily sync of all users
Roland Gruber created JENKINS-20671 Provide daily sync of all users Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ldap Created: 20/Nov/13 1:09 PM Description: We have some problems (especially with email sending) because there seems to be no automatic sync of all users on e.g. a daily basis. Jenkins sends out mails to users that no longer exist in LDAP. They should be removed. Please note, these mails are based on the user name (Subversion commit) and not generated by the mail notification post build action. Email addresses that are changed in LDAP are also not changed in Jenkins. It still uses the old value. Please provide a daily sync that updates the whole user list with the current LDAP data. Project: Jenkins Priority: Major Reporter: Roland Gruber 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] [plugin] (JENKINS-20659) Job Import plugin is unable to import jobs from cross linux platforms
martin naughton commented on JENKINS-20659 Job Import plugin is unable to import jobs from cross linux platforms do you have any logs of when this happens? upload the logs that have the information in it. also have a look at the Job Import plugin code to see what makes it decide when it isnt a valid project. 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-20630) Jenkins fails to start
Kerem Kat commented on JENKINS-20630 Jenkins fails to start +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] [core] (JENKINS-20630) Jenkins fails to start
Kerem Kat started work on JENKINS-20630 Jenkins fails to start Change By: Kerem Kat (20/Nov/13 1:44 PM) Status: Open InProgress 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-20630) Jenkins fails to start
Kerem Kat stopped work on JENKINS-20630 Jenkins fails to start Change By: Kerem Kat (20/Nov/13 1:44 PM) Status: InProgress Open 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-20673) Plugin checker validation does not work correctly
André Schramm created JENKINS-20673 Plugin checker validation does not work correctly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: coverity Created: 20/Nov/13 1:47 PM Description: Coverity is run via script, the plugin only fetches the defects afterwards. Console output: Coverity Found snapshot IDs 1234 Coverity Fetching defects for stream Foo Coverity Found 100 defects Coverity Found 58 defects matching all filters: [ ... ] Under "defect filters" everything is set including all 95 checkers, so all 100 defects should match IMHO. Environment: CentOS 5.4, Coverity 6.0.1 (Internal version numbers: 1.5222:3042, 20120412041511UTC, p-berkeley-push-11376.367), Jenkins 1.539 Project: Jenkins Priority: Critical Reporter: André Schramm 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-20673) Plugin defect filter does not work correctly
André Schramm updated JENKINS-20673 Plugin defect filter does not work correctly Change By: André Schramm (20/Nov/13 1:52 PM) Summary: Plugin checkervalidation defectfilter doesnotworkcorrectly 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-20674) Downgrading from Git plugin 2.0 to 1.1.29 is impossible
CharlesB created JENKINS-20674 Downgrading from Git plugin 2.0 to 1.1.29 is impossible Issue Type: Bug Assignee: Nicolas De Loof Components: git, git-client Created: 20/Nov/13 2:12 PM Description: After upgrading from 1.1.26 to 2.0, I faced issue #JENKINS-20356, whose fix is not yet released. As the issue is related to git-client plugin, I choose to switch back to the latest version that doesn't include it, being 1.1.29 according to the release notes. I uninstall plugin, and upload 1.1.29 manually, but installation fails: Nov 20, 2013 1:39:29 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin git java.io.IOException: Dependency git-client (1.0.1) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479) at hudson.PluginManager$2$1$1.run(PluginManager.java:354) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Environment: Jenkins stable ver. 1.509.4, on Ubuntu 12.04.3 LTS Project: Jenkins Priority: Major Reporter: CharlesB 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] [ownership] (JENKINS-19078) Ownership Plugin does not launch after restart
Oleg Nenashev resolved JENKINS-19078 as Wont Fix Ownership Plugin does not launch after restart I've added an info to plugin's page (v. 0.1 - 0.2 migration). After the manual cleanup, all other versions work fine. I've also added compatibility checkers to avoid such situations in future. I propose to leave this issue "as is" without code modifications. Do you agree with such approach, Hubert? Change By: Oleg Nenashev (20/Nov/13 2:22 PM) Status: Open Resolved Resolution: WontFix 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-client] (JENKINS-20387) Timeout (10min) on git clone command
Joseph S commented on JENKINS-20387 Timeout (10min) on git clone command Mark W - Thnx for the URL (https://updates.jenkins-ci.org/download/plugins/). 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-20630) Jenkins fails to start
Shannon Kerr commented on JENKINS-20630 Jenkins fails to start jagannath behera, you should never use a nightly build when you are just trying out a new software. Jenkins has LTS releases that are solid and should be used if you are just starting out. Also, I typically wait a day or two before moving to the latest nightly build to see what the community ratings are and if any major bugs are reported in the tracker. 1.539 has excellent ratings if you still want to use a nightly, bleeding edge, build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-12006) Branch specifier does not replace matrix build variables
Paul Murphy commented on JENKINS-12006 Branch specifier does not replace matrix build variables I would appreciate if this feature was considered for a future release. It would be very useful to parameterize the git branch from the matrix axis. It is possible to do this as a build parameter so it unfortunate that it is currently not possible to do this from a matrix axis. 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-19752) Download build artifacts as zip generates a corrupted file
Yoram Michaeli commented on JENKINS-19752 Download build artifacts as zip generates a corrupted file Happens to me as well in releases 1.536 1.540 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] [cli] (JENKINS-16197) Job run via cli with -s is not aborted on client abort
Vadim Strizhevsky commented on JENKINS-16197 Job run via cli with -s is not aborted on client abort I have the same issue. Is it possible to raise the priority of this as there's no workaround 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-18366) Jetty should be used rather than Winstone for embedded deployments
Benjamin Dewez
commented on JENKINS-18366
Jetty should be used rather than Winstone for embedded deployments
I have the same error with our Jenkins after an upgrade to 1.539. It extract the war file into our /tmp folder but this one is cleaned by some other process and I can't guarantee that all files will not be deleted... This is a horrible behavior for us and so, it's blocker.
Nov 20, 2013 3:29:14 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.y.z-SNAPSHOT
Nov 20, 2013 3:29:14 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Extract jar:file:/usr/lib/jenkins/jenkins.war!/ to /tmp/jetty-0.0.0.0-8181-jenkins.war-_jenkins-any-/webapp
Nov 20, 2013 3:29:16 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for /jenkins, did not find org.apache.jasper.servlet.JspServlet
Jenkins home directory: /data/jenkins found at: System.getProperty("JENKINS_HOME")
@dev, I have try to use your solution and I define another tmp folder for Jenkins but it still extract its war file into our /tmp folder.
Here an echo of my command line exectuded when I start the service.
Starting Jenkins
JAVA_CMD : /usr/java/java6/bin/java -Djava.awt.headless=true -XX:MaxPermSize=512M -Xms512m -Xmx4096m -DJENKINS_HOME=/data/jenkins -jar /usr/lib/jenkins/jenkins.war
PARAMS : --logfile=/data/logs/jenkins/jenkins.log --webroot=/data/jenkins/war --daemon --httpPort=8181 --ajp13Port=8010 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 -Djava.io.tmpdir=/data/jenkins/tmp --prefix=/jenkins --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined --simpleAccessLogger.file=/var/log/jenkins/access_log
Thx for any help
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-20392) Git plugin 2.0 Recent Changes is always empty in merge job
Kurtis Miller commented on JENKINS-20392 Git plugin 2.0 Recent Changes is always empty in merge job As a side effect of this, a developer who performs a bad merge may never actually appear in the changelog or be notified that their bad merge commit has broken the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Arek Jaworski created JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 20/Nov/13 2:59 PM Description: Today, I downloaded latest version of Jenkins (1.540). I have Java 1.7.0_45 installed on Windows 7. When I start Jenkins: java -jar jenkins.war it looks as it is starting and when the last message appears: INFO: Jenkins is fully up and running a message pops up saying: Java platform binary has stopped working and I can't connect to localhot:8080. I looked up this in the Internet and I found one similar issue reported on StackOverflow: http://stackoverflow.com/questions/20085795/java-tm-platform-binary-has-stopped-working-pop-up-arrived-during-starting-jekin This has been reported 13 hours ago from now (14:55 GMT). I tried to run Jenkins (1.540) on two different Win7 machines and on both it was crashing Java. I found a quick solution - simply use previous build of Jenkins (1.539). This one looks to be working fine (or at least it doesn't crash Java and I can connect to localhost:8080). Fix Versions: current Project: Jenkins Priority: Major Reporter: Arek Jaworski 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] [maven] (JENKINS-20676) Project configuration throws exception if maven module is disabled
justinas Urbanavicius created JENKINS-20676 Project configuration throws exception if maven module is disabled Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 20/Nov/13 3:12 PM Description: If you disable maven plugin, and open configuration of a project you will see jetty exception. It does not matter if project uses or not maven. Mine did not, but configuration page still tried to load maven, which was disabled as i don't use it. WARNING: Failed to load hudson.maven.MavenModuleSet java.lang.InstantiationException: java.lang.NoClassDefFoundError: Could not initialize class hudson.maven.MavenModuleSet$DescriptorImpl at net.java.sezpoz.IndexItem.instance(IndexItem.java:193) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:355) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:234) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:531) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:317) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.getComponents(ExtensionList.java:149) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at org.jenkinsci.plugins.xunit.AliasInitializer.addAliases(AliasInitializer.java:23) 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:616) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[JIRA] [core] (JENKINS-19752) Download build artifacts as zip generates a corrupted file
Yoram Michaeli reopened JENKINS-19752 Download build artifacts as zip generates a corrupted file Happens to me in 1.535, 1.536, 1.539 Change By: Yoram Michaeli (20/Nov/13 3:11 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jurica Krizanic commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Still occurs, Jenkins 1.540, Publish over SSH plugin 1.10 ! 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-9016) Git creates usernames based on 'name' not the email.
Dominik Drzewiecki commented on JENKINS-9016 Git creates usernames based on name not the email. In my setup I have users authenticated against corporate Active Directory, which works nice along with LDAP email plugin (email addresses get resolved correctly). User ids look something like 123456, and as such are defined in Global Security. Real user names do get resolved correctly from those numeric ids. Unfortunatelly, when it comes to build changes list of the git based projects, the real user names do not get resolved correctly as they do not contain those numeric ids any more. For the commiter/author "Dominik Drzewiecki dominik.drzewie...@acme.com" which is a concatenation of git user.name and user.email configuration parameters I get the changelog entry commited by dominik.drzewiecki which cannot be futher resolved either against AD (id) or LDAP (email). It seems that Jan's patch that adds one extra resolution step would do the trick. 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-20204) Future releases of Java 7 will block connecting slaves due to no permissions attribute in the JAR file
Theresa N commented on JENKINS-20204 Future releases of Java 7 will block connecting slaves due to no permissions attribute in the JAR file We have the same problem when starting the slave via java web start on Windows 7 with Java 7 Update 45, Jenkins 1.539. According to https://groups.google.com/d/msg/jenkinsci-users/dLr_1LRucGA/7W-nAnfenNAJ this can only be fixed by the one providing the jar and jnlp files. 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-19752) Download build artifacts as zip generates a corrupted file
Yoram Michaeli edited a comment on JENKINS-19752 Download build artifacts as zip generates a corrupted file Happens to me in 1.535, 1.536, 1.539 yorammi-macbook:temp Yoram$ unzip ../archive\ 3.zip Archive: ../archive (3).zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of ../archive (3).zip or ../archive (3).zip.zip, and cannot find ../archive (3).zip.ZIP, period. 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-9016) Git creates usernames based on 'name' not the email.
Dominik Drzewiecki updated JENKINS-9016 Git creates usernames based on name not the email. Change By: Dominik Drzewiecki (20/Nov/13 3:34 PM) Environment: gitplugin1.1.6 gitplugin2.0,jenkins1.540,ubuntu13.10 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1
José Barreto commented on JENKINS-20669 OrderRetainingMap bug: array index out of range : -1 alternative solution found 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1
José Barreto assigned JENKINS-20669 to Unassigned OrderRetainingMap bug: array index out of range : -1 Change By: José Barreto (20/Nov/13 3:37 PM) Assignee: JoséBarreto 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-20630) Jenkins fails to start
william schilp commented on JENKINS-20630 Jenkins fails to start i'm having the same problem, java crashes shortly after loading jenkins. rolling back fixes the problem. any idea when a fix will be available. i updated some of my plugins that now will not run because they need the newer jenkins. 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1 - ALTERNATIVE SOLUTION FOUND
José Barreto updated JENKINS-20669 OrderRetainingMap bug: array index out of range : -1 - ALTERNATIVE SOLUTION FOUND Change By: José Barreto (20/Nov/13 3:38 PM) Summary: OrderRetainingMapbug:arrayindexoutofrange:-1 -ALTERNATIVESOLUTIONFOUND 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] [cli] (JENKINS-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
SCM/JIRA link daemon commented on JENKINS-18058 NegativeArraySizeException when trying to enable a job using Jenkins CLI Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/5517471be4fb76398ff98707b2f37b2a80bef51e Log: JENKINS-18058 Merged #1016 for better diagnosis. Compare: https://github.com/jenkinsci/jenkins/compare/6586d779b165...5517471be4fb 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-20630) Jenkins fails to start
Jonathan Johnson commented on JENKINS-20630 Jenkins fails to start Shannon - Any typical consumer who lands on the main http://jenkins-ci.org/ page (typically via a search engine) will see on the right hand side "Latest and greatest" and all the various platform installers, all linking to build 1540. The information about downloading does not say untested, unstable, bleeding edge build it specifically states "and greatest". Most people would assume not to have to always go to the previous build or hunt user ratings. The Jenkins site should not put the onus on the hundreds+ consumers and instead the build should be pushed to the main site only when enough time has gone by or the users rating rise above some threshold. At minimum the site should remove the subjective marketing text "and greatest" since latest builds are not backed by data from user ratings and test validations. 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-tracker] (JENKINS-20669) OrderRetainingMap bug: array index out of range : -1 = Alternative Solution Found
José Barreto updated JENKINS-20669 OrderRetainingMap bug: array index out of range : -1 = Alternative Solution Found Change By: José Barreto (20/Nov/13 3:39 PM) Summary: OrderRetainingMapbug:arrayindexoutofrange:-1 -ALTERNATIVESOLUTIONFOUND =AlternativeSolutionFound 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-20560) Custom-tools plugin breaks path for android-emulator
Alexander Silgidjian commented on JENKINS-20560 Custom-tools plugin breaks path for android-emulator I also confirm that the patch is working. Thanks! 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-20630) Jenkins fails to start
william schilp commented on JENKINS-20630 Jenkins fails to start i strongly agree with Jonathan. in addition, the only reason i upgraded my installation of jenkins was due to a message on the jenkins control page that indicated a new version of jenkins was available. i thought (apparently incorrectly) that the jenkins control panel would only tell me that a new version was available if that version was a stable release. if that is not the case, then the message should say: New (possible unstable) version of Jenkins (x.x.x) is available for download. NOTE: use at your own risk. 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-20630) Jenkins fails to start
Shannon Kerr commented on JENKINS-20630 Jenkins fails to start Jonathan - Sure, I agree with you that there is no text on the site that explicitly states that there is danger in using the latest and greatest. I assumed as much when I first came to the site. The "Long-Term Support Release" does say "Older but stable" implying potential instability with the weekly Latest and Greatest. Also, this follows along with other projects that release stable LTS builds, while allowing those that want to, to run with the bleeding edge updates. Perhaps it's my months of experience using the weekly builds that I was also basing my comments on. I started out using the LTS and later moved to weekly builds for my sandbox instance. I've been burned multiple times and now assume that weekly builds are never guaranteed to work. I think it is a reasonable expectation that users will check Community ratings if they exist. A more visible warning would be a good idea. 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-client] (JENKINS-20677) HTTP URLs with variables are not supported when using credentials
Florian Zschocke
created JENKINS-20677
HTTP URLs with variables are not supported when using credentials
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git-client
Created:
20/Nov/13 4:12 PM
Description:
When using a variable in a repository URL and username-password credentials the authentication fails.
Example: http://example.com/git/${Repo}.git
The problem is that the URL is saved with the variable name but later compared with the URL where the variable has been replaced. This way the lookup fails and the credentials do not get selected.
Project:
Jenkins
Priority:
Major
Reporter:
Florian Zschocke
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-20603) Pipeline plugin NPE when users not yet logged in.
Steve Suehs updated JENKINS-20603 Pipeline plugin NPE when users not yet logged in. Change By: Steve Suehs (20/Nov/13 4:23 PM) Summary: Pipelineplugin NPEwhenusersnotyetloggedin. 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-6439) Timeline on BuildTimeTrend page does not work
D Soa reopened JENKINS-6439 Timeline on BuildTimeTrend page does not work This is not working in Jenkins ver. 1.537 or 1.539. Only the latest successful build is shown. No other data points on the graph. It does initially show the correct day, but the build is shown an hour later than it happened. Both the server and client are in the same timezone (CST). I'll try attaching a screenshot. Change By: D Soa (20/Nov/13 4:35 PM) Resolution: Fixed Status: Closed 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-20678) Separate Application/Configuration and User Data
nw created JENKINS-20678 Separate Application/Configuration and User Data Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 20/Nov/13 4:37 PM Description: Jenkins has only one top level folder containing everything. Many third-party web applications have a top level distinction between application/configuration and user data. Take for example Sonatype Nexus. It has two main folders - "nexus-x.x.x" and "nexus_data". More specifically, within Jenkins the file config.xml contains items that could be considered user data (most notably view definitions) as well as application-level configuration (pretty much everything else). This becomes problematic when attempting to manage a Jenkins instance programmatically (e.g. via Puppet). User changes must be added upstream before applying a configuration update. Environment: Centos 5.9 Fix Versions: current Project: Jenkins Priority: Major Reporter: nw 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-20461) Git Plugin 2.0: fails to clone repo
Ferry Huberts commented on JENKINS-20461 Git Plugin 2.0: fails to clone repo This happens because the 'prune' option is set while the repo is not yet cloned. this really is a bug: the prune should be skipped when the clone has not yet been done. it also is a regression. please fix asap (the 2.0 git plugin seems to have a lot of issues...) 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-6439) Timeline on BuildTimeTrend page does not work
D Soa updated JENKINS-6439 Timeline on BuildTimeTrend page does not work On version 1.537. Change By: D Soa (20/Nov/13 4:49 PM) Attachment: TimelineMissingDataWrongHour.jpg 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-20644) jenkins-cli failed to run disable/enable job with correct active directory username and password
Feng Dai updated JENKINS-20644 jenkins-cli failed to run disable/enable job with correct active directory username and password Change By: Feng Dai (20/Nov/13 4:50 PM) Summary: jenkins-cli faile failed torundisable/enablejobwithcorrectactivedirectoryusernameandpassword Environment: Linux2.6.35,Jenkins1.540,JenkinsActiveDirectoryPlugin1.33 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Bruce Coveny commented on JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 This is happening to us as well but we are running on a WAS server and it crashes the server and I cannot find a way to "downgrade" to 1.539 any suggestions? 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-20180) Jenkins fails to save configuration if invoking gradle file with: net.sf.json.JSONException: JSONObject[useWrapper] is not a JSONObject
Victor Baca resolved JENKINS-20180 as Fixed Jenkins fails to save configuration if invoking gradle file with: net.sf.json.JSONException: JSONObject[useWrapper] is not a JSONObject Resolved by JENKINS-20262 when reverting JENKINS-18629. Change By: Victor Baca (20/Nov/13 4:54 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] [core] (JENKINS-6439) Timeline on BuildTimeTrend page does not work
D Soa updated JENKINS-6439 Timeline on BuildTimeTrend page does not work This one shows only two data points. Still off by 1 hour. Change By: D Soa (20/Nov/13 4:59 PM) Attachment: ScreenShotWithTwoDataPoints.jpg 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] [plugin] (JENKINS-20679) Define manifest header in the jpi file to capture minimum JDK requirement
Kohsuke Kawaguchi created JENKINS-20679 Define manifest header in the jpi file to capture minimum JDK requirement Issue Type: Improvement Assignee: Unassigned Components: plugin Created: 20/Nov/13 4:59 PM Description: Some plugins depend on Java6 (either by compiled for Java6 for by having critical dependencies that are compiled for Java6) while others still work on Java5. The manifest should declare this so that the update center can warn users appropritely. 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-6439) Timeline on BuildTimeTrend page does not work
D Soa commented on JENKINS-6439 Timeline on BuildTimeTrend page does not work I attached another screenshot from a different project. It shows 2 data points, so it isn't limited to just the latest. Still off by 1 hour. 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-6439) Timeline on BuildTimeTrend page does not work
D Soa commented on JENKINS-6439 Timeline on BuildTimeTrend page does not work Upgraded to 1.540. Same problem. 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-20630) Jenkins fails to start
Gemini A commented on JENKINS-20630 Jenkins fails to start @Jonathan, I concur with you too. @William, yes I did the same as you. All current older Jenkins installation prompts admins looking at their "Manage Jenkins" page to upgrade to the latest 1.540 build. The message is highlighted at the top of the manage Jenkins page and clearly says: "New version of Jenkins (1.540) is available for download". It also draws your attention to it via a highlighted exclamation mark. There is no mention that this may be an unstable build. Also, if this is indeed something that people should not use "when you are just trying out a new software"... then imho there should be an explicit statement regarding this especially when it is the one being touted as the "Latest and Greatest" right in your face on the front-page of http://jenkins-ci.org and in the main *Release* tab. The fact that it says "Release" and not a development, nightly build, or even release candidate or beta software makes this, from my perspective, look like an official Release version. Most people won't even notice the "Long Term Support Release" tab. Just my two cents. 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-20630) Jenkins fails to start
Gemini A updated JENKINS-20630 Jenkins fails to start Change By: Gemini A (20/Nov/13 5:12 PM) Affects Version/s: current Environment: MicrosoftWindowsServer2003R2 MicrosoftWindows2008serverw/TomcatWinXPSP3 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] [core] (JENKINS-20630) Jenkins fails to start
loyal parsons commented on JENKINS-20630 Jenkins fails to start I have to wholeheartedly agree about both the website download linking and especially the prompting on the Manage Jenkins page. Perhaps these should both be submitted as issues? 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] [cli] (JENKINS-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
dogfood commented on JENKINS-18058 NegativeArraySizeException when trying to enable a job using Jenkins CLI Integrated in jenkins_main_trunk #3071 JENKINS-18058 Merged #1016 for better diagnosis. (Revision 5517471be4fb76398ff98707b2f37b2a80bef51e) Result = SUCCESS Jesse Glick : 5517471be4fb76398ff98707b2f37b2a80bef51e Files : changelog.html 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Hal Deadman commented on JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 I also was getting a JVM core dumps on Windows whether I ran with Java 6 on Tomcat 6 or Java 7 on Tomcat 7. I tried two different versions of Java 7 and the errors always occurred in the finalizer thread. (in java 6 or java 7). I backed off to version 1.539 and the problem went away. I will attach one of the dump log files. 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Hal Deadman updated JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 Sample dump file from Java 6 trying to start up with Jenkins 1.540. Since the crash occurs in the finalizer Jenkins would die at various points during startup depending on when it gc'd whatever it was that is killing JVM. I got similar crash with two different versions of Java 7 (including 1.7.0_45) too but I don't have the log files. Change By: Hal Deadman (20/Nov/13 5:23 PM) Attachment: hs_err_pid3196.log 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-19752) Download build artifacts as zip generates a corrupted file
Jesse Glick resolved JENKINS-19752 as Fixed Download build artifacts as zip generates a corrupted file @yorammi I already verified the fix in 1.536 so if you are seeing corrupt ZIP files it is probably some other bug, that may happen only under certain circumstances, etc. Please file a separate report with steps to reproduce from scratch. Change By: Jesse Glick (20/Nov/13 5:28 PM) Status: Reopened 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] [copyartifact] (JENKINS-20680) Remote triggering Copy Artifact build selector requires weird syntax
Attila-Mihaly Balazs created JENKINS-20680 Remote triggering Copy Artifact build selector requires weird syntax Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 20/Nov/13 5:36 PM Description: When triggering builds remotely like the following: /buildWithParameters?BUILD_NUMBER=123 I get the exception below. Finally I figured out that I need to wrap the build number into Xml tags like the following: /buildWithParameters?BUILD_NUMBER=StatusBuildSelector plugin="copyartifact@1.28"123/StatusBuildSelector However this seems cumbersome and I'm also not sure if it's future proof (if there is an update installed copyartifact, will it still work?) and it's more complicated than it needs to be. I would prefer for the first, simpler syntax to work. The exception I get is the following: javax.servlet.ServletException: com.thoughtworks.xstream.io.StreamException: : only whitespace content allowed before start tag and not a (position: START_DOCUMENT seen a... @1:1) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:92) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at
[JIRA] [core] (JENKINS-20681) Record time when a node is taken offline
Miroslav Cupak assigned JENKINS-20681 to Miroslav Cupak Record time when a node is taken offline Change By: Miroslav Cupak (20/Nov/13 5:44 PM) Assignee: MiroslavCupak 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-6439) Timeline on BuildTimeTrend page does not work
D Soa commented on JENKINS-6439 Timeline on BuildTimeTrend page does not work Checked a few other projects and a pattern has emerged. All builds before 6pm CST the previous day are missing from the graph. That's midnight GMT. So only builds from the current "GMT day" are shown (and then displayed one hour later than they happened). 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.
