[JIRA] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Andrew Erickson commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Steven, Joris, (or anyone with permissions - not sure where to see a list of people), Will you please publish a 1.5.4 with this latest fix? Thanks, Andy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17590) Builds fail because of "slave went offline during the build"
Andrew Erickson resolved JENKINS-17590 as Duplicate Builds fail because of "slave went offline during the build" duplicate, moving activity to JENKINS-16778 Change By: Andrew Erickson (31/May/13 5:57 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
Markus Strand commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished Now with version 0.12 the execution happens optionally on the matrix configurations, but there is no way to not run it on the head. I would agree with the requirement that it should be optional to: 1) Run a script at the end of each element of a matrix build. This is the current functionality. 2) Run a script at the end of a entire matrix build (ie. after all matrix elements have built). 3) A combination of 1 and 2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to snrkiwi71 Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:07 AM) Assignee: Sega snrkiwi71 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to Sega Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:07 AM) Assignee: Sega This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to Unassigned Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:07 AM) Assignee: Sega This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to Sega Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:05 AM) Assignee: Sega This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-17895) job enabled status should be preserved
Sylvain Benner resolved JENKINS-17895 as Fixed job enabled status should be preserved In 1.14 there is a new generation option for disable jobs. Patch: https://github.com/jenkinsci/jobgenerator-plugin/commit/3c638dde55011c3d045f647035f403c8e34f28fd Change By: Sylvain Benner (31/May/13 3:43 AM) Status: In Progress 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] [jobgenerator] (JENKINS-17843) Generation is slow
Sylvain Benner updated JENKINS-17843 Generation is slow Change By: Sylvain Benner (31/May/13 3:44 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18111) Discard old builds: links first build to 404 error
sogabe commented on JENKINS-18111 Discard old builds: links first build to 404 error You have to update to 1.497 or later. This bug was fixed in 1.497. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16201) Join plugin - join job does not run
Ishaaq Chandy commented on JENKINS-16201 Join plugin - join job does not run I've also been seeing this exact issue for a few versions now (I'm currently running version 1.515) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16023) Lazy loading causes massive delays after a period of inactivity when loading dashboard
dogfood commented on JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard Integrated in jenkins_main_trunk #2563 [FIXED JENKINS-16023] Use permalinks for as many Job.getLast*Build methods as possible. (Revision be5cd4fd169005f50eea8ccefac4b91a9b4c503c) Result = SUCCESS Jesse Glick : be5cd4fd169005f50eea8ccefac4b91a9b4c503c Files : test/src/test/java/hudson/model/JobTest.java core/src/main/java/hudson/model/Job.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [doxygen] (JENKINS-18154) HTML output directory is incorrect when folderWhereYouRunDoxygen is used
Kieron Briggs commented on JENKINS-18154 HTML output directory is incorrect when folderWhereYouRunDoxygen is used Patch submission: https://github.com/jenkinsci/doxygen-plugin/pull/5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [doxygen] (JENKINS-18154) HTML output directory is incorrect when folderWhereYouRunDoxygen is used
Kieron Briggs assigned JENKINS-18154 to Gregory Boissinot HTML output directory is incorrect when folderWhereYouRunDoxygen is used Change By: Kieron Briggs (30/May/13 11:46 PM) Assignee: Kieron Briggs Gregory Boissinot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [doxygen] (JENKINS-18154) HTML output directory is incorrect when folderWhereYouRunDoxygen is used
Kieron Briggs created JENKINS-18154 HTML output directory is incorrect when folderWhereYouRunDoxygen is used Issue Type: Bug Assignee: Kieron Briggs Components: doxygen Created: 30/May/13 11:34 PM Description: When the "folder where you run Doxygen" setting is used, the HTML_OUTPUT setting in the Doxyfile is interpreted relative to that location, instead of being relative to the OUTPUT_DIRECTORY setting (which itself is relative to the folderWhereYouRunDoxygen). This causes publication of the generated documentation to fail. Project: Jenkins Priority: Major Reporter: Kieron Briggs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-16207) "Changes Summary" diff link broken after migration to TFS 2012
steven armstrong commented on JENKINS-16207 "Changes Summary" diff link broken after migration to TFS 2012 Is this plugin not being worked on anymore? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16023) Lazy loading causes massive delays after a period of inactivity when loading dashboard
Jesse Glick updated JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard Change By: Jesse Glick (30/May/13 10:19 PM) Labels: lts-candidate performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16023) Lazy loading causes massive delays after a period of inactivity when loading dashboard
SCM/JIRA link daemon commented on JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Job.java test/src/test/java/hudson/model/JobTest.java http://jenkins-ci.org/commit/jenkins/be5cd4fd169005f50eea8ccefac4b91a9b4c503c Log: [FIXED JENKINS-16023] Use permalinks for as many Job.getLast*Build methods as possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16023) Lazy loading causes massive delays after a period of inactivity when loading dashboard
SCM/JIRA link daemon resolved JENKINS-16023 as Fixed Lazy loading causes massive delays after a period of inactivity when loading dashboard Change By: SCM/JIRA link daemon (30/May/13 10:11 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] [dependencyanalyzer] (JENKINS-7992) fails to parse dependency analysis results in recent hudson
Juan Manuel Formoso commented on JENKINS-7992 fails to parse dependency analysis results in recent hudson Hi guys, any news on a fix for 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] [maven] (JENKINS-18086) Add support for tests run by scalatest-maven-plugin
a b commented on JENKINS-18086 Add support for tests run by scalatest-maven-plugin Many thanks for the quick reviews and merging of the patches! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Eric Lordahl commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I saw this for the first time today, and saw it twice. Three things have changed over the past week that could possibly affect this. I'm wondering how many people who have this problem use an NFS share, for I've seen a lot of file contention issues since the change to NFS. 1. (Few weeks ago)$JENKINS_HOME is now an NFS share 2. (Last night)Updated to 1.516 3. (Last night)Modified github plugin to use a, already-defined, ThreadFactory (see below): -private transient final SequentialExecutionQueue queue = new SequentialExecutionQueue(Executors.newCachedThreadPool()); +private transient final SequentialExecutionQueue queue = new SequentialExecutionQueue(Computer.threadPoolForRemoting); This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
dogfood commented on JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session Integrated in jenkins_main_trunk #2561 [FIXED JENKINS-17684] Integrate new Winstone with caching fix. (Revision 0866cf5c190bcfc8f5b04dd9e335e7ca74bd4980) Result = SUCCESS Jesse Glick : 0866cf5c190bcfc8f5b04dd9e335e7ca74bd4980 Files : war/pom.xml changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-18153) Crowd2 Plugin Authenticates user, but does not log user in
jake plimack created JENKINS-18153 Crowd2 Plugin Authenticates user, but does not log user in Issue Type: Bug Affects Versions: current Assignee: Thorsten Heit Components: crowd2 Created: 30/May/13 9:06 PM Description: Users are allowed or denied with a good/bad pass, but the user is still not logged in after transaction. I've tried in multiple browsers on multiple computers and gotten the same result. I see failed logins in the logs, but not successful ones. Environment: Centos 6.3 Project: Jenkins Priority: Major Reporter: jake plimack This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-18152) Free space monitoring fails on slaves
Michael Chmielewski created JENKINS-18152 Free space monitoring fails on slaves Issue Type: Bug Assignee: Unassigned Components: master-slave Created: 30/May/13 8:17 PM Description: Periodically in the tomcat logs (and always on start up) I see the following stack trace. It seems to imply a version mismatch between the slave and master (can't deserialize an object)? May 30, 2013 4:03:44 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Failed to monitor h2_deuterium for Free Temp Space hudson.util.IOException2: remote file operation failed: /home/jenkins/hydrogen at hudson.remoting.Channel@d48ff87:h2_deuterium at hudson.FilePath.act(FilePath.java:900) at hudson.FilePath.act(FilePath.java:877) at hudson.node_monitors.TemporarySpaceMonitor$1.getFreeSpace(TemporarySpaceMonitor.java:73) at hudson.node_monitors.DiskSpaceMonitorDescriptor.monitor(DiskSpaceMonitorDescriptor.java:169) at hudson.node_monitors.DiskSpaceMonitorDescriptor.monitor(DiskSpaceMonitorDescriptor.java:49) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:246) Caused by: java.io.IOException: Remote call on h2_deuterium failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:893) ... 5 more Caused by: java.lang.Error: Failed to deserialize the Callable object. at hudson.remoting.UserRequest.perform(UserRequest.java:104) 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: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) Caused by: java.lang.reflect.UndeclaredThrowableException at $Proxy5.fetch2(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:127) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2442) at java.lang.Class.getDeclaredMethod(Class.java:1952) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1411) at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:69) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:481) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:455) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.(ObjectStreamClass.java:455) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:352) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:589) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1601) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1514) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1750) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1347) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1964) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1888) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1347) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) ... 8 more Caused by: java.lang.InterruptedE
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
SCM/JIRA link daemon resolved JENKINS-17684 as Fixed Dashboard web pages don't render correctly in Chrome because of bad cache/session Change By: SCM/JIRA link daemon (30/May/13 8:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
SCM/JIRA link daemon commented on JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session Code changed in jenkins User: Jesse Glick Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/0866cf5c190bcfc8f5b04dd9e335e7ca74bd4980 Log: [FIXED JENKINS-17684] Integrate new Winstone with caching fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
SCM/JIRA link daemon commented on JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session Code changed in jenkins User: Jesse Glick Path: src/java/winstone/WinstoneResponse.java src/test/winstone/WinstoneResponseTest.java http://jenkins-ci.org/commit/winstone/7e57b9d574818516c2a01c3807c60a90c4ea6594 Log: Merge pull request #9 from ikikko/master JENKINS-17684 Remove Content-Type header when 304 not modified. Compare: https://github.com/jenkinsci/winstone/compare/b844d0dc6b86...7e57b9d57481 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-18015) Breakage on Android SDK r22
Manfred Moser commented on JENKINS-18015 Breakage on Android SDK r22 Thanks for the work around.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Jesse Glick commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Maybe we are bundling a version of JNA which is too old? Is this 64-bit? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fxcop-runner] (JENKINS-18151) FxCop-Runner sets build results to unstable when FxCop runs succesfully
Michael Fowler created JENKINS-18151 FxCop-Runner sets build results to unstable when FxCop runs succesfully Issue Type: Bug Assignee: Unassigned Components: fxcop-runner Created: 30/May/13 6:07 PM Project: Jenkins Labels: plugin Priority: Major Reporter: Michael Fowler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-17876) MSBuild Command Line Arguments quotes being stripped...not 5552
Jonathan Zimmerman commented on JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 I had the same problem, that the quotes were being stripped from /p:Configuration="Release|x86". I believe the solution is to specifically use instantiate QuoteStringTokenizer instances that return the quotes instead of relying on ArgumentListBuilder.addTokenized() (which will strip the quotes). I've committed the changes to a fork and have submitted a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292"; alt=""
height="48" width="48" border="0" align="left" style="padding:0;margin: 0 16px
16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=m_broida";
style="color:#355564;">m_broida
commented on https://issues.jenkins-ci.org/images/icons/improvement.gif"; height="16"
width="16" border="0" align="absmiddle" alt="Improvement"> JENKINS-10841
Expose
submitter name to environment variable & views
Really really need the
submitter name as an envvar, or some workaround so job can use that
name.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, vi
[JIRA] [email-ext] (JENKINS-14040) After the build I want to trigger two e-mails
Alex Earl resolved JENKINS-14040 as Fixed After the build I want to trigger two e-mails Changed the way that triggers are added so that you can add multiple of the same trigger to the list. Change By: Alex Earl (30/May/13 4:44 PM) Status: In Progress 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] [email-ext] (JENKINS-14040) After the build I want to trigger two e-mails
Alex Earl started work on JENKINS-14040 After the build I want to trigger two e-mails Change By: Alex Earl (30/May/13 4:43 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18150) Symlinks to lastXBuild disappear
Paul Tipaldy created JENKINS-18150 Symlinks to lastXBuild disappear Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins-log.txt Components: core Created: 30/May/13 4:39 PM Description: Overnight, for the last two nights, the symlinks to all the lastXBuilds have broken – apparently spontaneously (without any builds taking place). They now refer to: jenkins@gsbuild:~/jobs/Gulfstream-build-vm/builds$ ls -la lrwxrwxrwx 1 jenkins nogroup 19 May 24 16:14 1 -> 2013-05-24_16-14-27 drwxr-xr-x 3 jenkins nogroup 4096 May 24 16:14 2013-05-24_16-14-27 ... lrwxrwxrwx 1 jenkins nogroup2 May 30 09:12 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins nogroup2 May 30 09:12 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins nogroup2 May 30 09:12 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins nogroup2 May 24 16:14 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins nogroup2 May 30 09:12 lastUnsuccessfulBuild -> -1 Although note that the actual job directories are still present, along with their job number links. Additionally, in the web UI, the build history is now empty. Starting a new job causes the build history to be populated correctly, and the symlinks to be updated appropriately. Expected behaviour is for the symlinks to always work, and for the history UI to always be populated with the last few jobs. I've attached my log file, in case that's useful. Project: Jenkins Priority: Major Reporter: Paul Tipaldy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
SCM/JIRA link daemon commented on JENKINS-18146 Support for comma separated fields for downstream jobs Code changed in jenkins User: syl20bnr Path: src/main/java/org/jenkinsci/plugins/jobgenerator/GeneratorRun.java http://jenkins-ci.org/commit/jobgenerator-plugin/adc0e4478b3a40d96a1eaf87c9329d27588c39d8 Log: JENKINS-18146 upport for comma separated fields for downstream jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
SCM/JIRA link daemon commented on JENKINS-18146 Support for comma separated fields for downstream jobs Code changed in jenkins User: syl20bnr Path: src/main/java/org/jenkinsci/plugins/jobgenerator/GeneratorRun.java http://jenkins-ci.org/commit/jobgenerator-plugin/333c09899b3a0c03e9784b9e59590a8e8d32e64e Log: JENKINS-18146 Support for comma separated fields for downstream jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-6651) Hudson crashes for unknown reasons
paalnilsen commented on JENKINS-6651 Hudson crashes for unknown reasons @evernat, we moved to Cloudbees a long time ago, so I wouldn't know. Sorry. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-17895) job enabled status should be preserved
Sylvain Benner started work on JENKINS-17895 job enabled status should be preserved Change By: Sylvain Benner (30/May/13 4:11 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-17895) job enabled status should be preserved
Sylvain Benner commented on JENKINS-17895 job enabled status should be preserved I'll add an option to enable/disable to generated jobs on the build action page (beside job only and delete options) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
Sylvain Benner resolved JENKINS-18146 as Fixed Support for comma separated fields for downstream jobs Fixed in 1.14 which will be release today Change By: Sylvain Benner (30/May/13 4:00 PM) Status: In Progress 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] [jobgenerator] (JENKINS-18143) In fields with job entries, a trailing comma prevent from generating the job names correctly
Sylvain Benner resolved JENKINS-18143 as Fixed In fields with job entries, a trailing comma prevent from generating the job names correctly Fixed with JENKINS-18146 Change By: Sylvain Benner (30/May/13 3:59 PM) Status: In Progress 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] [concurrent-build] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
evernat commented on JENKINS-13810 Maven modules marked to wrong build when running concurrent job Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-6651) Hudson crashes for unknown reasons
evernat commented on JENKINS-6651 Hudson crashes for unknown reasons @paalnilsen Is it reproduced with a recent Jenkins version, given the lock added in May 2012 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [libvirt-slave] (JENKINS-18149) Enable manually start of a JNLP-Controlled Slave without automatically shutdown
Dennis Ditte created JENKINS-18149 Enable manually start of a JNLP-Controlled Slave without automatically shutdown Issue Type: Improvement Affects Versions: current Assignee: Philipp Bartsch Components: libvirt-slave, libvirtslave Created: 30/May/13 3:49 PM Description: My Problem is that i have to start a slave manually to change something, e.g. installing new software, whatever. With a Windows-Slave which connects to Jenkins with a JNLP i can't do this because the Slave shutdown directly after starting (the JNLP is autostarting at boot). I need a way to start such a Slave manually without going to Jenkins-Config everytime to change the settings for this slave. Project: Jenkins Priority: Major Reporter: Dennis Ditte This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Niels Beekman commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Using OpenJDK 6 I see the following exception in the log: Failed to load native POSIX impl; falling back on Java impl. Stacktrace follows. java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': com.sun.jna.Native.open(Ljava/lang/String;)J at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) at com.sun.jna.Library$Handler.(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:366) at org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) at org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) at org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) at hudson.os.PosixAPI.(PosixAPI.java:41) at hudson.Util.resolveSymlink(Util.java:1240) at hudson.Util.resolveSymlinkToFile(Util.java:1166) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:346) at hudson.model.Run.(Run.java:294) at hudson.model.AbstractBuild.(AbstractBuild.java:184) at hudson.maven.AbstractMavenBuild.(AbstractMavenBuild.java:54) at hudson.maven.MavenModuleSetBuild.(MavenModuleSetBuild.java:136) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1122) at hudson.model.AbstractProject$1.create(AbstractProject.java:322) at hudson.model.AbstractProject$1.create(AbstractProject.java:320) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1059) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:455) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:717) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:451) at hudson.model.AbstractProject.onLoad(AbstractProject.java:316) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:753) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2542) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-18148) JUnit Test Result Report Silently Ignores Files With Old Timestamps?
Nathan Nutter created JENKINS-18148 JUnit Test Result Report Silently Ignores Files With Old Timestamps? Issue Type: Bug Assignee: Unassigned Components: junit Created: 30/May/13 3:23 PM Description: We recently had an issue where the clock on our Jenkins server was ahead by about 15 minutes which caused the test result files (that are generated on other machines and shared over NFS) to appear 15 minutes old to Jenkins. In one case where the test suite takes less than that 15 minutes it correctly guessed that something was wrong and displayed a message like: 10:20:01 Test reports were found but none of them are new. Did tests run? 10:20:01 For example, /gscmnt/gc13001/info/model_data/apipe-ci/workspace/0-Genome-Perl-Tests-Quick/PERL_VERSION=5.10/PERL_VERSION/5.10/test_results/Model/Tools/Validation/Sciclone.t.junit.xml is 15 min old However, for another test suite that takes about 40 minutes it appears to have just silently ignored old files which caused it to report all tests as passing despite one of the tests failing. From the console log: ... 18:40:08 * ./Model/Command/Services/WebApp/Core.t STDERR * 18:40:08 <> 18:40:08 <> 18:40:08 Job <5231505> is submitted to queue . 18:40:08 * ... 19:07:37 But then the test report make no mention of this test. It also appears to be missing about 6k tests from the normal 16k tests run. Allowing a test failure to be reported as success seems absolutely undermining. Is it possible I could have configured Jenkins to prevent this problem? Or is this possible a critical bug (that has a low? chance of occurring)? Environment: Jenkins ver. 1.511 Linux vm86.gsc.wustl.edu 2.6.32-36-server #79-Ubuntu SMP Tue Nov 8 22:44:38 UTC 2011 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 10.04.4 LTS Release:10.04 Codename: lucid Project: Jenkins Priority: Major Reporter: Nathan Nutter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
SCM/JIRA link daemon commented on JENKINS-18146 Support for comma separated fields for downstream jobs Code changed in jenkins User: syl20bnr Path: src/main/java/org/jenkinsci/plugins/jobgenerator/GeneratorRun.java http://jenkins-ci.org/commit/jobgenerator-plugin/4b650d144d05f6143a888fa5f0ab70b69dbc485c Log: JENKINS-18146 upport for comma separated fields for downstream jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Markus commented on JENKINS-14508 Default pre-send script in Jenkins Configuration Great! Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ci-game] (JENKINS-18147) Sonar Support
Brandon McKenzie created JENKINS-18147 Sonar Support Issue Type: Improvement Assignee: redsolo Components: ci-game Created: 30/May/13 3:03 PM Description: I would like to incorporate ci-game into a CI environment that makes use of both Jenkins and Sonar. Sonar (www.sonarsource.org) is an open-source quality management platform dedicated to continuous analysis of code, and runs tools that ci-game is known to support (Findbugs, PMD, Checkstyle in particular). In my environment, Sonar is configured as a post-build action in Jenkins. Rather than force Sonar users to redundantly configure the aforementioned Code Quality tools on Jenkins just for the ci-game to score with, could you please implement support for Sonar-detected issues, if possible? Project: Jenkins Priority: Major Reporter: Brandon McKenzie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
Sylvain Benner updated JENKINS-18146 Support for comma separated fields for downstream jobs Change By: Sylvain Benner (30/May/13 2:48 PM) Description: i.e. the field ofr downstream jobs. Add support for multiple jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
Sylvain Benner started work on JENKINS-18146 Support for comma separated fields for downstream jobs Change By: Sylvain Benner (30/May/13 2:48 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18146) Support for comma separated fields for downstream jobs
Sylvain Benner created JENKINS-18146 Support for comma separated fields for downstream jobs Issue Type: Bug Assignee: Sylvain Benner Components: jobgenerator Created: 30/May/13 2:47 PM Description: i.e. the field ofr downstream jobs. Add support for multiple jobs Project: Jenkins Priority: Critical Reporter: Sylvain Benner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-16473) Build Pipeline View stops working after upgrading to Jenkins 1.499
will soula commented on JENKINS-16473 Build Pipeline View stops working after upgrading to Jenkins 1.499 I update my jobs using Jenkins Job Builder and that uses the api to create and reconfigure jobs. I have seen the pipeline view become blank right after I updated a job within the pipeline. I had updated the first job several times without issue. Then I updated the last job in the pipeline and suddenly the view had no jobs or pipelines in it. When I went to the page I got the same stacktrace as the first commenter. I then downgraded to 1.2.3 and it is not as slick looking as the latest but it seems to work better. After updating a job with Jenkins Job Builder I still get the pipeline view as empty but if I refresh it a few times it always seems to come back. Here is the stack trace from 1.2.3: May 30, 2013 9:07:50 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: from.getBuildPipelineForm() in /view/Soap/view/soap-pipeline/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:216) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) at hudson.model.Run.onLoad(Run.java:319) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:602) at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:264) at java.util.AbstractMap$2$1.(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:103) at au.com.centrumsystems.hudson.plugin.util.BuildUtil.getDownstreamBuild(BuildUtil.java:59) at au.com.centrumsystems.hudson.plugin.buildpipeline.PipelineBuild.getDownstreamPipeline(PipelineBuild.java:173) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildForm.(BuildForm.java:90) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildForm.(BuildForm.java:91) at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.getBuildPipelineForm(BuildPipelineView.java:214) at sun.reflect.GeneratedMethodAccessor279.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.C
[JIRA] [subversion] (JENKINS-18048) "Caused by" link on downstream jobs does not work correctly
Kevin Phillips updated JENKINS-18048 "Caused by" link on downstream jobs does not work correctly Added a screen cap that illustrates the bug. Change By: Kevin Phillips (30/May/13 1:42 PM) Attachment: screen_cap.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactdeployer] (JENKINS-18145) Artifact deployer should respect the artifact retention policy in Jenkins rather than the job retention policy
Kevin Phillips created JENKINS-18145 Artifact deployer should respect the artifact retention policy in Jenkins rather than the job retention policy Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: artifactdeployer Created: 30/May/13 1:37 PM Description: Jenkins jobs have two sets of job retention policies: one for builds and one for build artifacts. The former seems to be designed to manage the build logs and history cached by Jenkins. The latter seems to be meant for managing the build artifacts produced by said build. Currently it appears that the artifact deployer plugin is designed to only look at the retention policy for builds and it ignores the retention policy for artifacts. This seems wrong to me. Example use case Suppose you want to have a different retention policy for a job for the builds than for the artifacts. For example, build logs tend to be relatively small (a few KB or MB) where as build artifacts tend to be relatively large (many MB or possibly GB) - as is the case in our job configurations. In this case what we'd like to do is configure the build retention policy so it is relatively long (e.g.: keep build logs for 30 days) but the artifact retention policy needs to be kept relatively low (e.g.: keep only the last 2 sets of artifacts). This all sounds fine and dandy, except that since the artifact deployer plugin only looks at the job retention policy it doesn't respect the smaller retention policy used for artifacts. The only way around this seems to be to lower the build retention policy to the same as the artifact policy - something which we would prefer not to do. As such I would recommend that the artifact deployer plugin either be modified such that it uses the correct policy settings for its purpose, or at the very least provide some kind of option in its configuration to specify which policy should be followed. Project: Jenkins Priority: Major Reporter: Kevin Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18143) In fields with job entries, a trailing comma prevent from generating the job names correctly
Sylvain Benner started work on JENKINS-18143 In fields with job entries, a trailing comma prevent from generating the job names correctly Change By: Sylvain Benner (30/May/13 1:00 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18143) In fields with job entries, a trailing comma prevent from generating the job names correctly
Sylvain Benner updated JENKINS-18143 In fields with job entries, a trailing comma prevent from generating the job names correctly Change By: Sylvain Benner (30/May/13 1:00 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18143) In fields with job entries, a trailing comma prevent from generating the job names correctly
Sylvain Benner created JENKINS-18143 In fields with job entries, a trailing comma prevent from generating the job names correctly Issue Type: Bug Assignee: Sylvain Benner Components: jobgenerator Created: 30/May/13 12:52 PM Description: For instance in the "Project to build" field of a "Trigger parameterized build on other porjects" publisher: mysub_job1, mysub_job2, This entry will make the generation fail to correctly compute generated job names for "mysub_job1" and "mysub_job2". Project: Jenkins Priority: Minor Reporter: Sylvain Benner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Jesse Glick commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process @nbeekman: usually it is AIX/HP-UX users with issues. If you are on Linux using Java 5/6 then the JNA library should be used to load readlink from libc, and on Java 7 for any platform java.nio.file should be used. From your stack trace it seems like every attempt to read symlinks normally failed: java.nio.file; JNA; and the LinuxPOSIX part of jna-posix (which should have printed something like Failed to load native POSIX impl to console); finally fall back to the crappiest method: forking /usr/bin/readlink. So something is seriously wrong with either your Java installation or the Jenkins method Util.resolveSymlink; check e.g. UtilTest.testSymlink in a debugger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [instant-messaging] (JENKINS-18144) Allow templating or reduce verbosity
wernight created JENKINS-18144 Allow templating or reduce verbosity Issue Type: Improvement Assignee: kutzi Components: instant-messaging Created: 30/May/13 12:52 PM Description: Typical summary log is: Project Example build #1234: STILL UNSTABLE in 1 min 12 sec: http://example.com/job/Example/1234/ The time for example is completely irrelevant for me in most cases. I usually wish only to see how many tests fails if it's unstable but else I really just care SUCCESS/FAILED. One way would be to hard code with a bit more succinct message. Another way would be to allow templating the message: Project $PROJECT_NAME build $BUILD_NUMBER: $STATUS: $PROJECT_URL $TESTS_RESULTS Project: Jenkins Priority: Minor Reporter: wernight This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18140) SVNKit 1.7.6 library used in Jenkins causes file contents SVN checkouts to become duplicated
kutzi resolved JENKINS-18140 as Duplicate SVNKit 1.7.6 library used in Jenkins causes file contents SVN checkouts to become duplicated As mentioned in the SVNKit issue already, this is tracked as JENKINS-14551 Change By: kutzi (30/May/13 12:50 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18142) MAJOR PredefinedGeneratorParameters xml elements are deleted during generation!
Sylvain Benner closed JENKINS-18142 as Cannot Reproduce MAJOR PredefinedGeneratorParameters xml elements are deleted during generation! Change By: Sylvain Benner (30/May/13 12:47 PM) Status: In Progress Closed Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13202) Artifact archiving from an ssh slave fails if symlinks are present
Jesse Glick commented on JENKINS-13202 Artifact archiving from an ssh slave fails if symlinks are present @chrisgwarp et al.: commenting on timing is fine but it does not help Jenkins developers make any progress since, again, we cannot test for you on AIX. You need to evaluate whether pull #770 makes a difference, e.g. by running https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/857/artifact/war/target/jenkins.war built from that branch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18142) MAJOR PredefinedGeneratorParameters xml elements are deleted during generation!
Sylvain Benner created JENKINS-18142 MAJOR PredefinedGeneratorParameters xml elements are deleted during generation! Issue Type: Bug Assignee: Sylvain Benner Components: jobgenerator Created: 30/May/13 12:23 PM Project: Jenkins Priority: Major Reporter: Sylvain Benner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18142) MAJOR PredefinedGeneratorParameters xml elements are deleted during generation!
Sylvain Benner started work on JENKINS-18142 MAJOR PredefinedGeneratorParameters xml elements are deleted during generation! Change By: Sylvain Benner (30/May/13 12:24 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [compact-columns] (JENKINS-15601) Main dashboard takes minutes to load in browser
Kevin Phillips commented on JENKINS-15601 Main dashboard takes minutes to load in browser Yes - this is correct. Everything else was kept consistent on the configuration during this change. The addition of a separate agent process on the same PC as the Jenkins master service to manage the job threads seems to have fixed the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18141) BuildParameters: Support for "Password"
Andrew Harmel-Law created JENKINS-18141 BuildParameters: Support for "Password" Issue Type: New Feature Affects Versions: current Assignee: Justin Ryan Components: job-dsl-plugin Created: 30/May/13 12:01 PM Description: We have added support for all the parameter types apart from password. For discussion of this and implementation notes, see the original pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/50 Project: Jenkins Priority: Minor Reporter: Andrew Harmel-Law This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18140) SVNKit 1.7.6 library used in Jenkins causes file contents SVN checkouts to become duplicated
Glenn Keith created JENKINS-18140 SVNKit 1.7.6 library used in Jenkins causes file contents SVN checkouts to become duplicated Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 30/May/13 11:48 AM Description: This is a bug that was logged with SVNKit however the fix has not been deployed with the jenkins subversion plugin. Please see this link for detail: http://issues.tmatesoft.com/issue/SVNKIT-368 My current version of Jenkins is 1.480.3 and the Jenkins Subversion Plug-in version 1.48. We are using Subverion 1.7.9 This appears to just require an update of the plugin with the latest SVNKit library for the error to be resolved. Project: Jenkins Priority: Major Reporter: Glenn Keith This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18111) Discard old builds: links first build to 404 error
Martin d'Anjou commented on JENKINS-18111 Discard old builds: links first build to 404 error I use 1.492 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Niels Beekman commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Fair enough, impossible to say without a stack dump from the issue reported I guess. A small note regarding "exotic" though, this problem occurred on a stock Ubuntu 12.0.4 with OpenJDK 7 installed using apt-get. This might impact more users than one might think. A related question: is there a specific reason that a process is launched to resolve a symlink? For example, could http://docs.oracle.com/javase/6/docs/api/java/io/File.html#getCanonicalPath%28%29 be used? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-17383) CVS plugin detect changes in 'rlog' but not in 'update'
G P commented on JENKINS-17383 CVS plugin detect changes in 'rlog' but not in 'update' This happens to me too. This is actually a very severe issue because it means that we cannot rely on the update mechanism anymore. I am astonished that this issue does not get a greater priority (for me I consider this "Blocking"). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [next-executions] (JENKINS-18139) Add SCMTrigger
Paul Tost created JENKINS-18139 Add SCMTrigger Issue Type: Improvement Assignee: Unassigned Attachments: nextexections.diff Components: next-executions Created: 30/May/13 9:37 AM Description: You should add the SCMTrigger. I use it with scheduling and I can not see the next execution. I have fixed it for me and attach the diff. Thanks Paul Project: Jenkins Labels: plugins Priority: Major Reporter: Paul Tost This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18111) Discard old builds: links first build to 404 error
sogabe updated JENKINS-18111 Discard old builds: links first build to 404 error Change By: sogabe (30/May/13 9:32 AM) Assignee: nkns165 Component/s: core Component/s: discard-old-build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18111) Discard old builds: links first build to 404 error
sogabe commented on JENKINS-18111 Discard old builds: links first build to 404 error What the version of Jenkins are you using? similar bugs fixed in 1.497. see JENKINS-16194. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-17555) Environment variables not set early enough (or at all?)
Christian Lipphardt edited a comment on JENKINS-17555 Environment variables not set early enough (or at all?) I am also affected by this bug. I am using the plugin to inject a config file and then link the location of it via a variable as a parameter in a maven 2/3 job. It is not resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-17555) Environment variables not set early enough (or at all?)
Christian Lipphardt commented on JENKINS-17555 Environment variables not set early enough (or at all?) I am also affected by this bug. We are using the plugin to inject a config file and then link the location of it via a variable as a parameter in a maven 2/3 job. It is not resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-metadata-plugin] (JENKINS-18063) Authentication support for repository
Gesh Markov assigned JENKINS-18063 to Gesh Markov Authentication support for repository Change By: Gesh Markov (30/May/13 8:34 AM) Assignee: rsandell Gesh Markov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-metadata-plugin] (JENKINS-18063) Authentication support for repository
Gesh Markov commented on JENKINS-18063 Authentication support for repository Yes, that's the only way at the moment. It is not very user-friendly I admit. I will keep this task open as a reminder to add 2 additional fields: "Username" & "Password", where password will be a real password field which obscures its input. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Gesh Markov closed JENKINS-18138 as Not A Defect Value is not stored as parameter for later use you're welcome. Change By: Gesh Markov (30/May/13 8:26 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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Olli Varis edited a comment on JENKINS-18138 Value is not stored as parameter for later use Thanks for swift reply! Exactly where can I see this info? EDIT: found it thanks a lot! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Olli Varis commented on JENKINS-18138 Value is not stored as parameter for later use Thanks for swift reply! Exactly where can I see this info? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-17734) "Claim Report" view reports Error Status: 500
Christian Åkerström commented on JENKINS-17734 "Claim Report" view reports Error Status: 500 I will fix this for the next version, although I personally have very limited time for the next weeks. If someone make a pull request with a fix, I will look at it with high priority. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Gesh Markov resolved JENKINS-18138 as Not A Defect Value is not stored as parameter for later use That's because it creates multiple parameters based on the name of the parameter name you supply. For example if you named the property "MY_JAR" then the selected version from the dropdown will be "MY_JAR_VERSION". Another one that might be interesting depending on what you want to achieve is: "MY_JAR_ARTIFACT_URL". You can see the full list in Jenkins the "Parameters" section of an execution of the job. Cheers, Gesh Change By: Gesh Markov (30/May/13 7:43 AM) Status: Open Resolved Fix Version/s: current Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-17973) TFS SCM Polling fails with :: FATAL: Parse error. Unable to find an item within a changeset
david clark resolved JENKINS-17973 as Duplicate TFS SCM Polling fails with :: FATAL: Parse error. Unable to find an item within a changeset Sorry, this IS a duplicate of JENKINS-16208 Change By: david clark (30/May/13 7:41 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-16208) TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset
david clark commented on JENKINS-16208 TFS SCM Polling: FATAL: Parse error. Unable to find an item within a changeset On further investigation, the commit message is the issue: I am using git-tf to send from my git repo to tfs. I had --metadata set to true. This converts your git commit messages like "blah" to something like: "Commit abcdef (Tue May 21 14:19:15 2013 +1000) Author: David Clark [redacted].com> Committer: David Clark [redacted].com> - blah " Which is causing the parse error in the polling. (Due to "---" it seems). BTW: for anyone with a repo in this state you can fix it by: 1. git tf configure --no-metadata 2. push a change OR using team explorer, edit the last change set comment to not contain "---" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-14089) JUnit report - Quarantine intermittent tests
Christian Åkerström commented on JENKINS-14089 JUnit report - Quarantine intermittent tests I like the idea, make a pull request when you think you are finished. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
