[JIRA] (JENKINS-16551) NPE during copy project
Krzysztof Malinowski created JENKINS-16551 NPE during copy project Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 30/Jan/13 1:28 PM Description: Trying to copy Maven project to a new one, upon pressing OK I get: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:50) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:126) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:272) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:175) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:140) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1021) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184) at
[JIRA] (JENKINS-16368) Hardcoded protocol in some links
vjuranek commented on JENKINS-16368 Hardcoded protocol in some links @kurzi: right, sorry (sorry to all, I replied in hurry and didn't read the discussion very carefully, also broken email were mentioned earlier in the discussion ) @jglick: as for broken reverse proxy, if I'm not mistaken, rootUrl for jelly pages (used e.g. in layout.jelly) is setup in Functions#initPageVariables() 1 and not from configured Jenkins URL 1 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/Functions.java#L167 This message is automatically generated by JIRA. 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-16552) Throttle plugin does not throttle sub jobs in matrix project
Fredrik Simonsson created JENKINS-16552 Throttle plugin does not throttle sub jobs in matrix project Issue Type: Bug Affects Versions: current Assignee: abayer Components: matrix, throttle-concurrents Created: 30/Jan/13 1:34 PM Description: Throttling is only applied on parent job. A shared and limited resource (e.g. the number of licences) needs to be used by several child jobs, split over several matrix jobs. Not all parts of the matrix job can be executed in parallel, but running in sequence is neither an option. The Throttle-concurrent addon do this kind of throttling, however it is only applied at the master job and not at the individual sub jobs, so instead of running 5-10 instances of the massively parallel job all 500 variants are queued up at once blocking other kinds of jobs from running. Project: Jenkins Priority: Major Reporter: Fredrik Simonsson This message is automatically generated by JIRA. 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-9471) If the libvirt plugin is installed you can't edit nodes
Philipp Bartsch updated JENKINS-9471 If the libvirt plugin is installed you cant edit nodes Change By: Philipp Bartsch (30/Jan/13 1:44 PM) Component/s: libvirt-slave This message is automatically generated by JIRA. 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-16550) Existing defaultTasks not executed
Jochen Hinrichsen commented on JENKINS-16550 Existing defaultTasks not executed While working on a workaround, i found the problem: if the project is not checked out into the workspace directly, but into a subfolder (say: trunk), the gradle wrapper ist started, the project is found and run, but gradle gets bent out of shape w/ regard to its internal root project/ project/ module/ folder setup, and does not find default tasks. Weird. Would expect an error message at least. When checking out into the workspace directly, everything works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16553) Heap space problem
Anup T S created JENKINS-16553 Heap space problem Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 30/Jan/13 1:44 PM Description: Hello Team, We are repeatedly getting heap space issue ,even after setting Xmx to 6144m while starting jenkins. May i know is there any other congiguration where cwe can look into? Also i want to know how to set JVM xmx and xms jenkins-slave.xml file Due Date: 30/Jan/13 12:00 AM Environment: Production Project: Jenkins Priority: Major Reporter: Anup T S This message is automatically generated by JIRA. 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-14617) libvirt-slave builds broken connection URI
Philipp Bartsch assigned JENKINS-14617 to Philipp Bartsch libvirt-slave builds broken connection URI Change By: Philipp Bartsch (30/Jan/13 1:47 PM) Assignee: mmornati PhilippBartsch This message is automatically generated by JIRA. 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-12523) Could not initialize class org.libvirt.Connect
Philipp Bartsch assigned JENKINS-12523 to Philipp Bartsch Could not initialize class org.libvirt.Connect Change By: Philipp Bartsch (30/Jan/13 1:47 PM) Assignee: PhilippBartsch This message is automatically generated by JIRA. 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-9471) If the libvirt plugin is installed you can't edit nodes
Philipp Bartsch assigned JENKINS-9471 to Philipp Bartsch If the libvirt plugin is installed you cant edit nodes Change By: Philipp Bartsch (30/Jan/13 1:47 PM) Assignee: PhilippBartsch This message is automatically generated by JIRA. 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-14468) Not reconnect if libvirt is restarted
Philipp Bartsch assigned JENKINS-14468 to Philipp Bartsch Not reconnect if libvirt is restarted Change By: Philipp Bartsch (30/Jan/13 1:47 PM) Assignee: mmornati PhilippBartsch This message is automatically generated by JIRA. 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-14468) Not reconnect if libvirt is restarted
Philipp Bartsch started work on JENKINS-14468 Not reconnect if libvirt is restarted Change By: Philipp Bartsch (30/Jan/13 1:48 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] (JENKINS-14617) libvirt-slave builds broken connection URI
Philipp Bartsch started work on JENKINS-14617 libvirt-slave builds broken connection URI Change By: Philipp Bartsch (30/Jan/13 1:48 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] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Philipp Bartsch started work on JENKINS-12523 Could not initialize class org.libvirt.Connect Change By: Philipp Bartsch (30/Jan/13 1:48 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] (JENKINS-16553) Heap space problem
Anup T S commented on JENKINS-16553 Heap space problem Also how long will the http://server/jenkins/heapDump run? This message is automatically generated by JIRA. 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-16510) NPE on Maven3 Project - after Upgrading from 1.489 to 1.500
Steven Crellin edited a comment on JENKINS-16510 NPE on Maven3 Project - after Upgrading from 1.489 to 1.500 I have the same problem on a Maven2 project, without the PHP maven plugin. I suspected the "Publish xUnit test result report" post-build action, but the job still fails with no post-build actions at all This message is automatically generated by JIRA. 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-16552) Throttle plugin does not throttle sub jobs in matrix project
Fredrik Simonsson assigned JENKINS-16552 to Unassigned Throttle plugin does not throttle sub jobs in matrix project Change By: Fredrik Simonsson (30/Jan/13 1:58 PM) Assignee: abayer This message is automatically generated by JIRA. 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-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
Marco Rothe created JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 30/Jan/13 2:13 PM Description: The upgrade of the Commons Codec lib from 1.4 to 1.7 with Jenkins 1.500 break the compatibility to build with JDK5. The build fails with INFO ERROR FATAL ERROR INFO INFO Failed to load org.apache.commons.codec.DecoderException Bad version number in .class file INFO INFO Trace java.lang.ClassFormatError: Failed to load org.apache.commons.codec.DecoderException at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:193) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:144) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.Thread.run(Thread.java:595) ... Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.lang.ClassLoader.defineClass(ClassLoader.java:466) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:191) Replacing Commons Codec 1.7 with 1.6 seems to fix the problem. On the Commons Codec site (http://commons.apache.org/codec/) the following compatibility notes can be found: Codec 1.7 requires Java 1.6 Codec 1.6 requires Java 1.5 Codec 1.5 requires Java 1.4 So please downgrade to Commons Codec 1.6 if possible. Environment: SunOS 5.10, JDK5 Project: Jenkins Priority: Major Reporter: Marco Rothe This message is automatically generated by JIRA. 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-16206) Upgrade to Apache Commons Codec 1.7
Marco Rothe reopened JENKINS-16206 Upgrade to Apache Commons Codec 1.7 The upgrade breaks the compatibility with JDK5 (see JENKINS-16554). So please of Commons Codec 1.6 if achievable. Change By: Marco Rothe (30/Jan/13 2:21 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] (JENKINS-12556) Weather report for matrix builds
Fredrik Simonsson assigned JENKINS-12556 to Kohsuke Kawaguchi Weather report for matrix builds Is anyone maintaining matrix projects? Change By: Fredrik Simonsson (30/Jan/13 2:34 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. 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-16487) Promotion Level being set to INITIAL
Jens Brejner commented on JENKINS-16487 Promotion Level being set to INITIAL Hi Ronan. Aha, now I understand. Currently we follow ClearCase defaults with respect to the names and order of enumeration. What is your list of values for attribute PromotionLevel ? Best regards Jens Brejner This message is automatically generated by JIRA. 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-16555) Create iframe portlet
Karol Kański assigned JENKINS-16555 to Karol Kański Create iframe portlet Change By: Karol Kański (30/Jan/13 2:38 PM) Assignee: PeterHayes KarolKański This message is automatically generated by JIRA. 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-16555) Create iframe portlet
Karol Kański created JENKINS-16555 Create iframe portlet Issue Type: New Feature Assignee: Peter Hayes Components: dashboard-view Created: 30/Jan/13 2:38 PM Description: A portlet with an iframe presenting content from specified URL can be an useful addition to the dashboard view plug-in. One of its application can be presenting Sonar statistics for jobs from the view. Project: Jenkins Priority: Major Reporter: Karol Kański This message is automatically generated by JIRA. 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-16555) Create iframe portlet
Karol Kański started work on JENKINS-16555 Create iframe portlet Change By: Karol Kański (30/Jan/13 2:42 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] (JENKINS-16545) Duplicated lines in Graphviz
wolfs commented on JENKINS-16545 Duplicated lines in Graphviz Could you send me the config.xml or send me a screenshot of the configuration of the corresponding jobs? The graphviz file would also be helpful. This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Linards L commented on JENKINS-15156 Builds disappear from build history after completion For me fix, using v1.494 was simply copy excisting faulty job to new one. Probably the renaming of job / project causes this. The ridicilous side effect of this is that there are no validation check for current build number and just created / successfuly built and archived artifacts. If there would be simple excistance check that would valida that last build actually created artifacts and they ARE ACCESSIBLE to user, In my build system that would be pretty minor issue. Currently hitting on this is pretty pain-in-ass catogrizable one... Always wonder why to implement new features instead of simply avoid / fix blockers lurking everywhere in jenkins core :/ This message is automatically generated by JIRA. 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-16499) NPE when new job by copy from existing one
SCM/JIRA link daemon commented on JENKINS-16499 NPE when new job by copy from existing one Code changed in jenkins User: kstutz Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryActionFactory.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryJobListenerTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/5739007a07ce8f1f3ef111652450f7af045bc686 Log: Workaround for JENKINS-16499 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Ivaylo Bratoev commented on JENKINS-15156 Builds disappear from build history after completion As a matter of fact I renamed these builds some time ago as well... This might be one part of the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16487) Promotion Level being set to INITIAL
Ronan Mulvaney commented on JENKINS-16487 Promotion Level being set to INITIAL Hi Jens, We use the following levels: REJECTED INITIAL SMOKETESTED CIBUILD CIBUILD_FAILED CIBUILD_PASSED BUILT PEERSIGNOFF TESTED RELEASED However our issue here we have configured the job to avoid setting anything on the VOB therefore would like to ensure that the job isn't trying to change the promotion level like it is doing now, not that we want these added for usage. 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] (JENKINS-15156) Builds disappear from build history after completion
Richard Merrill commented on JENKINS-15156 Builds disappear from build history after completion I have had this issue occur without ever renaming any jobs, so I'm afraid the bug is a little more complicated. When it does happen, it is often for more than one job. Without doing anything, the problem can disappear the next time I open the web interface. Or sometimes it is more persistent and doesn't go away until I reload configuration from disk. I have versions 1.497 and 1.500 running on two separate WS2008R2 servers and it has happend on both. Fortunately, it hasn't happened very often lately... This message is automatically generated by JIRA. 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-15852) Unable to delete workspace
Daniel Kirkdorffer commented on JENKINS-15852 Unable to delete workspace We already had an exclusion setup for the Jenkins workspaces. My monitoring of the workspace folder using Process Explorer showed that wish.exe was the one holding on to it. I don't believe that gets called unless I use gitk.cmd. This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Linards L commented on JENKINS-15156 Builds disappear from build history after completion Ok. First of all - devs got to understand the point this nonsense started. On my second machine, using v1.454, this has never happened. Others ... ? Seems like Jenkins infrastructure does not have any way to do some regression tests ... like, for example, WineHQ guys got ... This message is automatically generated by JIRA. 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-15852) Unable to delete workspace
Linards L commented on JENKINS-15852 Unable to delete workspace Just ENSURE NO ONE GOT ANY KIND OF DAMN windows hangle / lock on that directory. Thats it. if you play nice and dont mess with workspace, Jenkins will be nice, too ... This message is automatically generated by JIRA. 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-15852) Unable to delete workspace
Linards L edited a comment on JENKINS-15852 Unable to delete workspace Just ENSURE NO ONE GOT ANY KIND OF DAMN windows handle / lock on that directory. Thats it. if you play nice and dont mess with workspace, Jenkins will be nice, too ... This message is automatically generated by JIRA. 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-16319) Failure to delete old config files during rekeying on Windows
David Odren reopened JENKINS-16319 Failure to delete old config files during rekeying on Windows An upgrade from Jenkins 1.497 to 1.500 produced the same errors about failure to rewrite the config.xml files. I am running Jenkins as a service on Windows 7. Change By: David Odren (30/Jan/13 3:45 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] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
David Odren edited a comment on JENKINS-16319 Failure to delete old config files during rekeying on Windows An upgrade from Jenkins 1.497 to 1.500 produced the same errors about failure to rewrite the config.xml files. I am running Jenkins as a service on Windows Server 2003 R2 Standard Edition SP2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16545) Duplicated lines in Graphviz
Mário Celso Teixeira updated JENKINS-16545 Duplicated lines in Graphviz Job Exception-1.0 config.xml file Change By: Mário Celso Teixeira (30/Jan/13 3:54 PM) Attachment: config.xml This message is automatically generated by JIRA. 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-16545) Duplicated lines in Graphviz
Mário Celso Teixeira updated JENKINS-16545 Duplicated lines in Graphviz Job Exception-1.0 Graphviz file generated Change By: Mário Celso Teixeira (30/Jan/13 3:55 PM) Attachment: graph.gv This message is automatically generated by JIRA. 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-1454) Maven2: AssertionError: reporters.get == null
Javatar 007
commented on JENKINS-1454
Maven2: AssertionError: reporters.get == null
I do confirm, in our chain we have in the 2nd job maven target: cobertura:cobertura ${mvn_opts}
And the ${mvn_opts} is set in the 1st job of the chain with maven_opts="-P PROFILE1"
The result:
INFO Preparing cobertura:cobertura
INFO
ERROR FATAL ERROR
INFO
INFO reporters.get(com.bobo:module1)==null. reporters={com.bobo:ROOT=[hudson.maven.reporters.MavenArtifactArchiver@1d838d9, hudson.maven.reporters.MavenSiteArchiver@13d07ff, hudson.maven.reporters.MavenTestJavadocArchiver@1d81be9, hudson.maven.reporters.MavenJavadocArchiver@11081d1, hudson.maven.reporters.SurefireArchiver@baf94e, hudson.maven.reporters.BuildInfoRecorder@14582b8, hudson.maven.reporters.MavenFingerprinter@2ce1f6]} proxies={com.bobo:ROOT=hudson.maven.AbstractMavenBuilder$FilterImpl@89371a}
INFO
INFO Trace
java.lang.AssertionError: reporters.get(com.bobo:module1)==null. reporters={com.bobo:ROOT=[hudson.maven.reporters.MavenArtifactArchiver@1d838d9, hudson.maven.reporters.MavenSiteArchiver@13d07ff, hudson.maven.reporters.MavenTestJavadocArchiver@1d81be9, hudson.maven.reporters.MavenJavadocArchiver@11081d1, hudson.maven.reporters.SurefireArchiver@baf94e, hudson.maven.reporters.BuildInfoRecorder@14582b8, hudson.maven.reporters.MavenFingerprinter@2ce1f6]} proxies={com.bobo:ROOT=hudson.maven.AbstractMavenBuilder$FilterImpl@89371a}
at hudson.maven.Maven2Builder.postModule(Maven2Builder.java:126)
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:340)
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:296)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:185)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:153)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
INFO
INFO Total time: 13 seconds
INFO Finished at: Wed Jan 30 14:59:27 CET 2013
INFO Final Memory: 39M/95M
INFO
En attente que Jenkins finisse de récupérer les données
channel stopped
Finished: FAILURE
This message is automatically generated by JIRA.
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-16556) Plugin deploy after update
Bruno Cunha created JENKINS-16556 Plugin deploy after update Issue Type: Improvement Assignee: Unassigned Components: update-center Created: 30/Jan/13 4:25 PM Description: Hello! I'm updating some plugins on the Update Center, and using the option "Install without restart", it often gives me a lot of errors like this: Subversion Plugin Falha - hudson.util.IOException2: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1259) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1056) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Unable to delete C:\Jenkins\plugins\subversion\WEB-INF\lib\antlr-runtime-3.4.jar at hudson.Util.deleteFile(Util.java:243) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:284) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:284) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.Util.deleteRecursive(Util.java:284) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:425) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:122) at hudson.PluginManager.dynamicLoad(PluginManager.java:391) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1255) ... 7 more But I guess Jenkins doesn't need to delete this JAR... The new version of plugin have the same JAR (same hash/fingerprint) compared to the older... It would be very good if Jenkins could check the target file before trying to replace that on the plugin deploy. This JPI files fingerprint improvement will make the updating experience looks better, and with less reboots. Thank you! Regards, Bruno Candido Volpato da Cunha Environment: Jenkins 1.498, JDK 1.6.0_31 64 bits - Windows Server 2008 R2 Project: Jenkins Labels: plugin deploy Priority: Major Reporter: Bruno Cunha This message is automatically generated by JIRA. 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-16535) vSphereCloud plugin doesn't work with vSphere 5.1
Jason Swager assigned JENKINS-16535 to Jason Swager vSphereCloud plugin doesnt work with vSphere 5.1 Change By: Jason Swager (30/Jan/13 4:30 PM) Assignee: JasonSwager This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
jenkinsuserfrance jenkinsuserfrance commented on JENKINS-15156 Builds disappear from build history after completion Hello, We had a similar problem with v 1.483. It happened on several jobs which were never renamed. Reloading the configuration restored the situation for most jobs. For few, some builds were missing in the history. After analysis, the missing builds were also lacking the build.xml in the "build/TimeStamp" folder. This message is automatically generated by JIRA. 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-16535) vSphereCloud plugin doesn't work with vSphere 5.1
Jason Swager commented on JENKINS-16535 vSphereCloud plugin doesnt work with vSphere 5.1 Can you give me more details of the problem? We've been using the plugin with vSphere 5.1 for over a month now without problem. According to the files you sent, it appears that you're not letting Jenkins start the VM, but waiting for someone else to start it. Try checking "Force VM Launch" This message is automatically generated by JIRA. 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-7294) Included regions feature for GIT
banoss commented on JENKINS-7294 Included regions feature for GIT There is now an includes region in the Git plugin as of v1.1.16. Should this be closed? This message is automatically generated by JIRA. 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-16499) NPE when new job by copy from existing one
Kathi Stutz commented on JENKINS-16499 NPE when new job by copy from existing one Using Yordan's code, I released a workaround for the JobConfigHistory plugin today. It catches the NPE, which is still thrown by the core. This message is automatically generated by JIRA. 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-16557) Git changes reported if in excluded regions
banoss created JENKINS-16557 Git changes reported if in excluded regions Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 30/Jan/13 5:08 PM Description: This has been discussed for subversion plugin and probably others too. But not seen an issue for the git plugin. Add a path to the excluded regions section of the plugin. Make a change inside the excluded region. Kick off a build manually. The change in the excluded region is listed for this build. Not a build is not kicked off by this change - the polling honours the excluded region. It's just the changeset reported that's the problem. And hence the confusion. Environment: Centos 6.2, Jenkins 1.492, Git plugin 1.126, git 1.7.5.GIT Project: Jenkins Labels: git scm polling Priority: Major Reporter: banoss This message is automatically generated by JIRA. 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-12408) paramaterized-triggers do not cooperate with cloudbees Folders to see jobs in the current folder.
cjo9900 resolved JENKINS-12408 as Fixed paramaterized-triggers do not cooperate with cloudbees Folders to see jobs in the current folder. Change By: cjo9900 (30/Jan/13 5:12 PM) Status: Open Resolved Assignee: huybrechts cjo9900 Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12408) paramaterized-triggers do not cooperate with cloudbees Folders to see jobs in the current folder.
cjo9900 commented on JENKINS-12408 paramaterized-triggers do not cooperate with cloudbees Folders to see jobs in the current folder. Closing as should have been fixed in 2.13 by commit https://github.com/jenkinsci/parameterized-trigger-plugin/commit/693c20eb1140d77e7dd1075fa52a0164fc4667f1 This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Julian Taylor commented on JENKINS-15156 Builds disappear from build history after completion for me it happens since lazy loading of build records was introduced, so version 1.485. I haven't verified that reverting back to 84 fixes it. the issue of jenkinsuserfrance in 483 is probably something else, because the build/ folder is perfectly alright it just does not load whats in there. This message is automatically generated by JIRA. 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Bruce Edge commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I have the same problem. It triggers soft lockups in the kernel of the jenkins host: 901 Jan 30 02:31:58 build kernel: 589969.228931 INFO: rcu_sched detected stall on CPU 3 (t=57719 jiffies) 902 Jan 30 02:31:58 build kernel: 589969.228939 INFO: rcu_sched detected stall on CPU 2 (t=57719 jiffies) 903 Jan 30 02:31:58 build kernel: 589969.228929 INFO: rcu_sched detected stall on CPU 1 (t=57719 jiffies) 904 Jan 30 02:31:58 build kernel: 589969.228944 INFO: rcu_sched detected stall on CPU 4 (t=57719 jiffies) 905 Jan 30 02:31:58 build kernel: 589969.228939 sending NMI to all CPUs: Note the timestamp correlation between the exception below and the stalls above. 712 Jan 30, 2013 2:31:58 AM org.kohsuke.stapler.compression.CompressionFilter reportException 6713 WARNING: Untrapped servlet exception 6714 winstone.ClientSocketException: Failed to write to client 6715 at winstone.ClientOutputStream.write(ClientOutputStream.java:41) 6716 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) 6717 at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) 6718 at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:165) 6719 at winstone.WinstoneOutputStream.flush(WinstoneOutputStream.java:217) 6720 at winstone.WinstoneOutputStream.close(WinstoneOutputStream.java:227) 6721 at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:241) 6722 at org.kohsuke.stapler.compression.FilterServletOutputStream.close(FilterServletOutputStream.java:36) 6723 at net.bull.javamelody.FilterServletOutputStream.close(FilterServletOutputStream.java:46) This happens most nights at the same time. This message is automatically generated by JIRA. 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-14529) BindException when using --daemon with JMX
Jesse Glick commented on JENKINS-14529 BindException when using --daemon with JMX Note: fix only available in JDK 7u4+: http://bugs.sun.com/view_bug.do?bug_id=7110104 This message is automatically generated by JIRA. 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-16368) Hardcoded protocol in some links
Jesse Glick commented on JENKINS-16368 Hardcoded protocol in some links Huh. Well if the current Stapler request is used to create a server-absolute URL then definitely reverse proxies would be broken unless the context path happens to match on each side. Not sure why this does not use Jenkins.rootUrl when defined. (Or use ../ multiplied by the depth of the current URI relative to the context root.) There seem to be several contradictory ways of resolving URLs and no clear guidance on which should be preferred and why. Maybe @Kohsuke can explain it all. This message is automatically generated by JIRA. 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-16319) Failure to delete old config files during rekeying on Windows
Jesse Glick commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows @dodren I reproduced the originally reported bug and confirmed the fix. If you are still seeing an issue the you need to provide the stack trace, with current line numbers. This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Jesse Glick commented on JENKINS-15156 Builds disappear from build history after completion Right, it is entirely possible there are two or more unrelated bugs lumped together here: at least, one present already in older versions of unknown cause; and one triggered by job renaming in 1.485+. This message is automatically generated by JIRA. 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-15045) Support Github commit status API
SCM/JIRA link daemon commented on JENKINS-15045 Support Github commit status API Code changed in jenkins User: Nicolas De loof Path: src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java http://jenkins-ci.org/commit/github-plugin/ef22d0173c0139a8d7f5531480befc3f94a5efc9 Log: Merge pull request #23 from jenkinsci/commit-status-api FIXED JENKINS-15045 Commit status API Compare: https://github.com/jenkinsci/github-plugin/compare/c566697220f7...ef22d0173c01 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15045) Support Github commit status API
SCM/JIRA link daemon resolved JENKINS-15045 as Fixed Support Github commit status API Change By: SCM/JIRA link daemon (30/Jan/13 6:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
bbonn commented on JENKINS-15156 Builds disappear from build history after completion Hi all, I have found a way to reproduce in our environment. Not sure if this will be the same for all of you, but maybe it is a start for debugging. I noticed recently that while un-shelving a job (plugin we use quite frequently) a job that was running displayed a strange 404 error in the console. See below 15:27:09 WARNINGS Parsing warnings in console log... 15:27:09 Archiving artifacts Status Code: 404 Exception: Stacktrace: (none) I then went back job page and refreshed and the build had disappeared. A reload from disk brought it back as usual. I have recreated a couple of times now, so not sure if the Shelve plugin is the culprit or some other underlying piece that interacts with plugins. Also, I don't always get the 404 in the console, sometimes after starting a un-shelving job, the link for the build console goes right tot a generic 404 error page. Jenkins 1.480.1 Windows Server 2008 R2 (Master and Slave) Can anyone else recreate this way? This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Jesse Glick commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 Probably several unrelated bugs here. This message is automatically generated by JIRA. 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-14588) Cannot query a job's git branch through xml api
Jason Marshall commented on JENKINS-14588 Cannot query a jobs git branch through xml api I have the same problem with other fields in the GitSCM object. Despite being processed in the constructor and exposed via @Exported, they return empty lists. This message is automatically generated by JIRA. 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-14588) Cannot query a job's git branch through xml api
Jason Marshall edited a comment on JENKINS-14588 Cannot query a jobs git branch through xml api I have a similar problem with other fields in the GitSCM object. Despite being processed in the constructor and exposed via @Exported, they return empty lists. I filed a bug covering the 'repositories' field as JENKINS-16558 This message is automatically generated by JIRA. 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-16558) Cannot get the repositories from the git plugin via the API
Jason Marshall
created JENKINS-16558
Cannot get the repositories from the git plugin via the API
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
30/Jan/13 7:53 PM
Description:
I'm trying to write a plugin that needs information from SCM plugins.
I'm having trouble extracting information from the Git plugin. I think it has some bugs that are causing it to not report data even though there's a great good deal of code in there to generate the answers.
Specifically, I can't find any incantation of scm/api/json that returns useful data in the repositories attribute. It seems to be an empty list. JENKINS-14588 reports that the 'branches' field is also empty. I'm curious if the root cause is similar for both or if they're separate issues.
{
"browser" : null,
"type" : "hudson.plugins.git.GitSCM",
"branches" : [
{
}
],
"mergeOptions" : {
"mergeRemote" : null,
"mergeTarget" : null,
"remoteBranchName" : null
},
"repositories" : [
{
}
],
"userRemoteConfigs" : [
{
"name" : "",
"refspec" : "",
"url" : "ssh://git-server:29418/projectname"
}
]
}
Project:
Jenkins
Labels:
plugin
scm
plugins
Priority:
Major
Reporter:
Jason Marshall
This message is automatically generated by JIRA.
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-16492) Upgrade from 0.12 to 0.13 breaks server
Bradley Wagner commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server Yea, confirmed here too. Thanks for the quick steps to resolve, Mark Takacs! This message is automatically generated by JIRA. 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-16319) Failure to delete old config files during rekeying on Windows
Damien Finck commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows It works for me on Jenkins 1.500 ! Windows Server 2008r2 Jenkins 1.500 This message is automatically generated by JIRA. 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-16319) Failure to delete old config files during rekeying on Windows
cforce commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows For me too! This message is automatically generated by JIRA. 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-16559) Build api doesn't include git repository
Jason Marshall
created JENKINS-16559
Build api doesnt include git repository
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
30/Jan/13 8:28 PM
Description:
If you pull the JSON for a build, you will see the branch name and the SHA1 hash for the commit but you won't see the repository url anywhere.
This makes life difficult if you're trying to watch more than one project, as you can't disambiguate by the repository.
{
"buildsByBranchName" : {
"origin/master" : {
"buildNumber" : 1813,
"buildResult" : null,
"revision" : {
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"branch" : [
{
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"name" : "origin/master"
}
]
}
},
"origin/mri" : {
"buildNumber" : 50,
"buildResult" : null,
"revision" : {
"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513",
"branch" : [
{
"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513",
"name" : "origin/mri"
}
]
}
}
},
"lastBuiltRevision" : {
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"branch" : [
{
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"name" : "origin/master"
}
]
},
Project:
Jenkins
Labels:
jenkins
git
build
scm
Priority:
Major
Reporter:
Jason Marshall
This message is automatically generated by JIRA.
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-16319) Failure to delete old config files during rekeying on Windows
Jesse Glick resolved JENKINS-16319 as Fixed Failure to delete old config files during rekeying on Windows @dodren I am reclosing; if you can still reproduce please file a fresh bug with a complete rekeying log and link it to this one. You might have hit some other problem needing a separate fix. Change By: Jesse Glick (30/Jan/13 8:32 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] (JENKINS-16165) Configure screen stuck in LOADING state
Vincent Latombe resolved JENKINS-16165 as Fixed Configure screen stuck in LOADING state Fixed in 1.3.14 Change By: Vincent Latombe (30/Jan/13 8:46 PM) Status: Open Resolved Assignee: stephenconnolly VincentLatombe Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16492) Upgrade from 0.12 to 0.13 breaks server
Kræn Hansen commented on JENKINS-16492 Upgrade from 0.12 to 0.13 breaks server I can confirm this issue. It blocked me right after the upgrade. This message is automatically generated by JIRA. 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-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2
David Odren created JENKINS-16560 Failure to rewrite files during rekeying on Windows Server 2003 R2 Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jan/13 9:49 PM Description: In an upgrade from Jenkins 1.487 to 1.500 the rekey operation fails due to being unable to rewrite the necessary files. This seems to be the same or similar to the issue resolved in JENKINS-16319, which was included in the Jenkins 1.500 release. I seem to be unable to upgrade beyond Jenkins 1.497, as this problem first occurred in an attempted upgrade from Jenkins 1.497 to 1.498. The re-key log is as follows: Started re-keying Wed Jan 09 10:13:00 CST 2013 Scanning E:\Jenkins\config.xml ERROR: Failed to rewrite E:\Jenkins\config.xml java.io.IOException: Unable to delete E:\Jenkins\config.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:121) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:143) at jenkins.security.RekeySecretAdminMonitor$RekeyThread.run(RekeySecretAdminMonitor.java:182) Scanning E:\Jenkins\jobs\BuildAllFromTrunk\builds\2012-12-11_06-16-44\changelog.xml Scanning E:\Jenkins\jobs\MakeCustomerService\builds\2012-12-15_06-40-38\changelog.xml Scanning E:\Jenkins\jobs\MakeCustomerService\builds\2013-01-08_06-40-28\changelog.xml Scanning E:\Jenkins\jobs\MakeFlash\builds\2012-12-29_07-07-22\build.xml Scanning E:\Jenkins\jobs\MakeImageOne\builds\2012-12-18_10-16-06\changelog.xml Scanning E:\Jenkins\jobs\MakeMsgProc\builds\2012-12-11_07-07-21\build.xml Scanning E:\Jenkins\jobs\MakeMsgProc\builds\2013-01-03_05-35-18\build.xml Scanning E:\Jenkins\jobs\MakePortal\builds\2012-12-20_07-21-50\changelog.xml Scanning E:\Jenkins\jobs\MakePrintAndPopcorn\builds\2012-12-13_10-33-18\build.xml Scanning E:\Jenkins\jobs\MakePrintAndPopcorn\builds\2013-01-05_07-07-37\build.xml Scanning E:\Jenkins\jobs\MakeTools\builds\2012-12-19_06-41-33\changelog.xml Scanning E:\Jenkins\jobs\MakeWeb\builds\2012-12-13_05-35-40\build.xml Scanning E:\Jenkins\jobs\MakeWeb\builds\2013-01-05_05-34-53\build.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-13_07-01-20\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-15_07-01-41\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-20_06-16-43\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2012-12-27_07-01-46\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2013-01-03_05-31-58\changelog.xml Scanning E:\Jenkins\jobs\RefreshBranchSourceCode\builds\2013-01-08_05-31-46\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-11_06-16-45\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-13_06-01-10\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-14_06-48-53\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-15_07-01-37\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-18_07-00-54\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-20_06-16-38\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-24_09-27-10\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-28_05-31-39\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2012-12-30_06-16-41\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2013-01-03_05-59-52\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2013-01-05_06-48-03\changelog.xml Scanning E:\Jenkins\jobs\UnregisterAllBranches\builds\2013-01-08_06-16-39\changelog.xml ERROR: Failed to rewrite E:\Jenkins\proxy.xml java.io.IOException: Unable to delete E:\Jenkins\proxy.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:121) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170) at
[JIRA] (JENKINS-13637) Cannot release using M3
Graham Leggett commented on JENKINS-13637 Cannot release using M3 Just hit this problem, and was forced to hack into settings.xml to work around it. This creates the situation where in our environment, it is not possible to build a jenkins plugin using a jenkins triggered build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16165) Configure screen stuck in LOADING state
Vincent Latombe assigned JENKINS-16165 to C S Configure screen stuck in LOADING state Change By: Vincent Latombe (30/Jan/13 10:11 PM) Assignee: VincentLatombe CS This message is automatically generated by JIRA. 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-16529) Provide the ability to turn off one time force sync after a failed build
Patrick McKeown commented on JENKINS-16529 Provide the ability to turn off one time force sync after a failed build Looked into this more, found this http://jenkins.361315.n4.nabble.com/Perforce-force-syncing-for-no-reason-td2993189.html It's not super obvious (I had issues similar to yours for a while), but Hudson automatically cleans up old workspaces that it thinks are stale... which works for some SCMs, but does not work well for Perforce at all in a configuration with multiple slaves. (Basically what happens, I think: Two slaves A and B are in use. The last build of job Foo was on A, while the last build on B was old in the eyes of the Workspace Cleanup thingy. The workspace for build B is cleaned. Job Foo has a submitted change. Hudson polls with Perforce on slave A and finds there is a change. If slave A's executors are unavailable, the build is started on B. As far as Perforce knows, the workspace on B is there and only needs the updates since it's last old build. But, in fact, because it has been cleaned up, that's not enough.) You are probably aware of this, but thought I'd share. This message is automatically generated by JIRA. 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-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
suresh nallamilli created JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull Issue Type: Bug Affects Versions: current Assignee: suresh nallamilli Attachments: popupErrorMsg.jpg Components: core Created: 30/Jan/13 11:45 PM Description: Getting warning message in a popup saying "Failed to evaluate. Invalid arguments" for jelly form control validateButton. I am getting this pop up irrespective of actual result of validation. This is happening only in Internet Explorer(8 and 9). This is not getting reproduced when running jenkins using "mvn hpi:run" but getting reproduced when running jenkins using command "java -jar jenkins.war" and then manually importing hpi file from advanced tab. For complete details , refer to discussion in https://groups.google.com/forum/#!topic/jenkinsci-dev/h4vlO8SkA60 Sample to reproduce this issue is available in my github https://github.com/sureshreddygithub/jenkinssamples.git or alternatively you can install https://wiki.jenkins-ci.org/display/JENKINS/SCTMExecutor plugin and try to validate in global configuration in IE. Root cause: For validate button form control , implementation is available @ scripts/hudson-behavior.js In validate function , we are using a custom function geval which is causing the issue. If i replace geval with eval i see that everything works as expected in IE as well. I will be submitting the fix in git shortly Environment: Windows 2008 R2 64 bit , Internet Explorer (8 and 9) Project: Jenkins Labels: plugin _javascript_ Priority: Blocker Reporter: suresh nallamilli This message is automatically generated by JIRA. 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-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
suresh nallamilli commented on JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull I was asked my Jesse Glick to mark this issue as "blocking" JENKINS-15617 to capture the relationship. I am not sure how to do that. Can some one take care of this This message is automatically generated by JIRA. 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-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
suresh nallamilli stopped work on JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull Change By: suresh nallamilli (30/Jan/13 11:48 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] (JENKINS-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
suresh nallamilli started work on JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull Change By: suresh nallamilli (30/Jan/13 11:48 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] (JENKINS-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
suresh nallamilli started work on JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull Change By: suresh nallamilli (31/Jan/13 12:32 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] (JENKINS-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
suresh nallamilli stopped work on JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull Change By: suresh nallamilli (31/Jan/13 12:33 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] (JENKINS-16562) Installing a new plugin jpi file via CLI does not really install without restart
Indra Gunawan
created JENKINS-16562
Installing a new plugin jpi file via CLI does not really install without restart
Issue Type:
Bug
Assignee:
Unassigned
Components:
cli, plugin
Created:
31/Jan/13 12:59 AM
Description:
I issued a install plugin command to install a plugin .jpi file on my local box using Jenkins CLI onto the Jenkins instance in the Data Center.
The command returned 0 (success) but it only copied the .jpi plugin file in the ${JENKINS_HOME}/plugins directory. I am thinking that it should copy, and install it right away without restart.
Command issue:
bash-3.2$ ./install-plugin1.sh sjc-bld120-lnx timestamper.jpi
jenkins = sjc-bld120-lnx
login to sjc-bld120-lnx ...
installing timestamper.jpi to sjc-bld120-lnx ...
Installing a plugin from local file: /Users/ingunawa/Data/Jenkins/plugins/timestamper.jpi
bash-3.2$ echo $?
0
the bash script simply login me with my credential and install-plugin; I am administrator of the Jenkins:
java -jar /Users/ingunawa/Data/Jenkins/jenkins-cli.jar -s http://$n:8080 login --username ingunawa --password-file cec-password.txt
java -jar /Users/ingunawa/Data/Jenkins/jenkins-cli.jar -s http://$n:8080 install-plugin /Users/ingunawa/Data/Jenkins/plugins/$PLUGIN;
jenkins.log:
Jan 30, 2013 4:49:15 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO: Accepted connection #6 from /10.21.69.43:64363
Jan 30, 2013 4:49:25 PM hudson.TcpSlaveAgentListener$ConnectionHandler run
INFO: Accepted connection #7 from /10.21.69.43:64398
-Indra
Environment:
Jenkins 1.455, on RHEL with Winstone.
Project:
Jenkins
Priority:
Major
Reporter:
Indra Gunawan
This message is automatically generated by JIRA.
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-16474) jenkins v1.484 - Universally slow page load times/hangs
Maxfield Stewart commented on JENKINS-16474 jenkins v1.484 - Universally slow page load times/hangs FYI we found a change note in Jenkins 1.482 indicating that the number of worker threads was reduced to 10 from 1000. We traced our issue to this problem. We can resolve it by upping the thread count the winstone container is using. We set the min threads to 50 and the max threads to 500. This message is automatically generated by JIRA. 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-16181) Jenkins does not try to resend a failed e-mail
Slide-O-Mix resolved JENKINS-16181 as Fixed Jenkins does not try to resend a failed e-mail Added a retry on SocketException occuring. Change By: Slide-O-Mix (31/Jan/13 4:27 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16181) Jenkins does not try to resend a failed e-mail
SCM/JIRA link daemon commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptorTest.java http://jenkins-ci.org/commit/email-ext-plugin/3af25cc2606cf0147376870d32de5930521e6a6f Log: Fix JENKINS-16181 Added a retry on SocketException occuring Added commented out main descriptor test, this will be used later Compare: https://github.com/jenkinsci/email-ext-plugin/compare/52dae3a93c5a...3af25cc2606c You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Nickolay Martinov commented on JENKINS-15156 Builds disappear from build history after completion Not sure this is caused by renaming as we do not rename jobs but had this problem very frequently (because of the number of jobs). Reverting back to version before 1.485 made this problem disappear. This is, imho, clear sign that lazy loading could be culprit. BTW, we don't have shelve plug-in. This message is automatically generated by JIRA. 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-16563) Build on every online node builds on nodes marked as offline
Alex Vesely created JENKINS-16563 Build on every online node builds on nodes marked as offline Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 31/Jan/13 5:48 AM Description: I have a job that triggers certain "cleaning" jobs on every node available to Jenkins (using the "Build on every online node" parameter factory). During the day, I noticed that one of my nodes became unstable for some reason, so I marked it as offline, so no builds were running on it. However, the parameter factory still created a build to run on the offline node. It was hanging in the queue, waiting for the node to come back online. I believe this behavior contradicts the factory description. Environment: JENKINS 1.480.1 LTS Project: Jenkins Priority: Major Reporter: Alex Vesely This message is automatically generated by JIRA. 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-16529) Provide the ability to turn off one time force sync after a failed build
Rob Petti commented on JENKINS-16529 Provide the ability to turn off one time force sync after a failed build That issue was fixed back in 1.3.11. Rather than triggering a force-sync, the plugin flushes the deleted workspace's client spec to revision 0, so it will only resync the workspace that was deleted. I can only see this causing issues if for some reason you have configured your plugin to share the same client spec across multiple slaves. This message is automatically generated by JIRA. 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-16036) Failed to record SCM polling for hudson.model.FreeStyle = NullPointerException
Bruce Edge commented on JENKINS-16036 Failed to record SCM polling for hudson.model.FreeStyle = NullPointerException I'm seeing the same thing with the latest version of everything, jenkins 1.500. Jan 30, 2013 10:45:20 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@5964dd7bServer-3.6 java.lang.IllegalArgumentException: Map must not be null at org.apache.commons.collections.map.AbstractMapDecorator.init(AbstractMapDecorator.java:63) at org.apache.commons.collections.map.UnmodifiableMap.init(UnmodifiableMap.java:73) at org.apache.commons.collections.map.UnmodifiableMap.decorate(UnmodifiableMap.java:62) at org.jenkinsci.lib.envinject.EnvInjectAction.getEnvMap(EnvInjectAction.java:42) at org.jenkinsci.plugins.envinject.EnvInjectBuildVariableContributor.buildVariablesFor(EnvInjectBuildVariableContributor.java:41) at hudson.model.AbstractBuild.getBuildVariables(AbstractBuild.java:1049) at hudson.model.AbstractBuild.getBuildVariableResolver(AbstractBuild.java:1058) at hudson.model.ParametersAction.createVariableResolver(ParametersAction.java:104) at hudson.model.ParametersAction.substitute(ParametersAction.java:89) at hudson.scm.SubversionSCM$ModuleLocation.getExpandedRemote(SubversionSCM.java:2400) at hudson.scm.SubversionSCM$ModuleLocation.getExpandedLocation(SubversionSCM.java:2447) at hudson.scm.SubversionSCM.getLocations(SubversionSCM.java:440) at hudson.scm.SubversionSCM.getLocations(SubversionSCM.java:400) at hudson.scm.SubversionSCM.buildEnvVars(SubversionSCM.java:607) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:941) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1230) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1493) at hudson.model.AbstractProject.poll(AbstractProject.java:1410) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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) Jan 30, 2013 10:46:20 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@698c415fServer-3.4 java.lang.IllegalArgumentException: Map must not be null at org.apache.commons.collections.map.AbstractMapDecorator.init(AbstractMapDecorator.java:63) at org.apache.commons.collections.map.UnmodifiableMap.init(UnmodifiableMap.java:73) at org.apache.commons.collections.map.UnmodifiableMap.decorate(UnmodifiableMap.java:62) at org.jenkinsci.lib.envinject.EnvInjectAction.getEnvMap(EnvInjectAction.java:42) at org.jenkinsci.plugins.envinject.EnvInjectBuildVariableContributor.buildVariablesFor(EnvInjectBuildVariableContributor.java:41) at hudson.model.AbstractBuild.getBuildVariables(AbstractBuild.java:1049) at hudson.model.AbstractBuild.getBuildVariableResolver(AbstractBuild.java:1058) at hudson.model.ParametersAction.createVariableResolver(ParametersAction.java:104) at hudson.model.ParametersAction.substitute(ParametersAction.java:89) at hudson.scm.SubversionSCM$ModuleLocation.getExpandedRemote(SubversionSCM.java:2400) at hudson.scm.SubversionSCM$ModuleLocation.getExpandedLocation(SubversionSCM.java:2447) at hudson.scm.SubversionSCM.getLocations(SubversionSCM.java:440) at hudson.scm.SubversionSCM.getLocations(SubversionSCM.java:400) at hudson.scm.SubversionSCM.buildEnvVars(SubversionSCM.java:607) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:941) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1230) at
[JIRA] (JENKINS-16537) Investigate whether Sauce support can be programatically enabled for slave nodes
Ross Rowe created JENKINS-16537 Investigate whether Sauce support can be programatically enabled for slave nodes Issue Type: Improvement Assignee: Ross Rowe Components: sauce-ondemand Created: 30/Jan/13 7:59 AM Project: Jenkins Priority: Major Reporter: Ross Rowe This message is automatically generated by JIRA. 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-14128) Workspaces not getting cleaned upon build completion
Thomas Fields commented on JENKINS-14128 Workspaces not getting cleaned upon build completion Thanks for the fix. It's working great. This message is automatically generated by JIRA. 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-15449) IE 9 os is wrong
Ross Rowe resolved JENKINS-15449 as Fixed IE 9 os is wrong The latest version of the plugin should be including the platform as an unconverted value now, so the platform for IE9 should be correct Change By: Ross Rowe (30/Jan/13 8:02 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] (JENKINS-15598) Include support for linking Sauce Job to Test result by parsing 'job-name'
Ross Rowe started work on JENKINS-15598 Include support for linking Sauce Job to Test result by parsing job-name Change By: Ross Rowe (30/Jan/13 8:03 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] (JENKINS-15449) IE 9 os is wrong
Ross Rowe started work on JENKINS-15449 IE 9 os is wrong Change By: Ross Rowe (30/Jan/13 8:02 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] (JENKINS-16049) Include job name in list of Sauce jobs for a test result
Ross Rowe started work on JENKINS-16049 Include job name in list of Sauce jobs for a test result Change By: Ross Rowe (30/Jan/13 8:03 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] (JENKINS-16049) Include job name in list of Sauce jobs for a test result
Ross Rowe resolved JENKINS-16049 as Fixed Include job name in list of Sauce jobs for a test result Change By: Ross Rowe (30/Jan/13 8:05 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] (JENKINS-16538) Resource remains sporadically locked
Massimo Rossello created JENKINS-16538 Resource remains sporadically locked Issue Type: Bug Affects Versions: current Assignee: rsandell Components: external-resource-dispatcher Created: 30/Jan/13 8:08 AM Description: The resource remains sporadically locked in spite of a successful release on log Collecting metadata... Metadata collection done. Releasing previously locked resource: 0019001200190071... Resource 0019001200190071 successfully released. Finished: SUCCESS Possibly the root cause can be the same as JENKINS-16302 Environment: Jenkins 1.478 external-resource-dispatcher 1.0b metadata 1.0b Project: Jenkins Priority: Major Reporter: Massimo Rossello This message is automatically generated by JIRA. 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-16165) Configure screen stuck in LOADING state
Martin Helff commented on JENKINS-16165 Configure screen stuck in LOADING state Hi Vincent, this is working now, 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] (JENKINS-16534) Copy existing Job - Status Code: 500 - NullPointerException
Stefan Brausch assigned JENKINS-16534 to Stefan Brausch Copy existing Job - Status Code: 500 - NullPointerException Change By: Stefan Brausch (30/Jan/13 8:27 AM) Assignee: MirkoFriedenhagen StefanBrausch This message is automatically generated by JIRA. 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-16539) *.jenkins-ci.org are not accessible via IPV6
Andrew West created JENKINS-16539 *.jenkins-ci.org are not accessible via IPV6 Issue Type: Bug Assignee: Unassigned Components: www Created: 30/Jan/13 9:01 AM Description: As per title. None of the sites are accessible via IPV6, and while this is a trivial matter for the most part it does prevent automatic updates via Linux package managers using pkg.jenkins-ci.org. Project: Jenkins Priority: Trivial Reporter: Andrew West This message is automatically generated by JIRA. 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-14786) Build.xml file missing for every builds using Publish Klocwork test result report
Steven Aerts commented on JENKINS-14786 Build.xml file missing for every builds using Publish Klocwork test result report I am seeing this problem too, it can be reproduced by running klocwork on a non-master node and enabling the "Parse Log" checkbox in your configuration. When the job is finished and tries to persis its build.xml, this exception will occur. This message is automatically generated by JIRA. 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-16372) Password parameter is malformed
Mateusz Balbus closed JENKINS-16372 as Fixed Password parameter is malformed Verified on version 1.81, works fine. Did you notice that now password is visible in logs? I'm guessing it is core issue now. Change By: Mateusz Balbus (30/Jan/13 9:08 AM) Status: Resolved Closed This message is automatically generated by JIRA. 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-16533) Jobs checked out from svn with pinned externals continuously run (with no changes in svn)
kutzi commented on JENKINS-16533 Jobs checked out from svn with pinned externals continuously run (with no changes in svn) I wonder why the unit test created for JENKINS-6209 does not fail, when there's a regression This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Sam Reghenzi commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 Same problem on both winxp and centos 6.3 jenkins version 1.5.0 GRAVE: Failed Loading job SOR-EAG java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DE SC: lo=3,hi=0,size=5,size2=5 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunM ap.java:421) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:213) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.jav a:349) at hudson.model.Run.onLoad(Run.java:318) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap .java:645) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap .java:628) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunM ap.java:435) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoa dRunMap.java:300) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1021) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMave nProject.java:184) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.j ava:688) at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:411) at hudson.model.AbstractProject.onLoad(AbstractProject.java:300) at hudson.maven.MavenModule.onLoad(MavenModule.java:236) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:748) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2539) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuild er.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:889) 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$Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) This message is automatically generated by JIRA. 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.
