[JIRA] (JENKINS-16333) Cancel in the queue widget tends to cause 404
Kohsuke Kawaguchi created JENKINS-16333 Cancel in the queue widget tends to cause 404 Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Jan/13 8:03 AM Description: It's because the link is by the ID of the queue item, and by the time the user clicks it, it might have already been gone. It should handle this more gracefully. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16319) Failure to delete old config files during rekeying on Windows
Wolf Wolfswinkel commented on JENKINS-16319 Failure to delete old config files during rekeying on Windows This seems to be similar to the issues reported in https://groups.google.com/d/topic/jenkinsci-users/hBRb8XqNQyM/discussion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16310) Source code loses spacing/indenting due to html white space collapsing.
Ognjen Bubalo commented on JENKINS-16310 Source code loses spacing/indenting due to html white space collapsing. Hi, Hmm as far as I know I solved this problem. It is interesting that you loose indentation. It would be good if I could somehow reproduce the problem, or have a printscreen. If non of these are possible I'll create a test release soon with this include in the css so we can check it. Thanks, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16316) global variable not updated
Nicolas De Loof resolved JENKINS-16316 as Fixed global variable not updated Change By: Nicolas De Loof (14/Jan/13 9:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16330) Trigger should start two jobs, but one is never started
rsandell commented on JENKINS-16330 Trigger should start two jobs, but one is never started Yes this is a tricky situation for the trigger; it needs to coordinate what jobs it has scheduled but (from what I can find) can't know if the job was canceled while in the queue, if that happens it will wait forever for the build to start (that's when it sends the build started message to Gerrit) Do you have any plugins that might cancel jobs in the queue? or maybe users that does it manually? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16334) Define impllicit parameter: "build them on the same node"
Kohsuke Kawaguchi created JENKINS-16334 Define impllicit parameter: "build them on the same node" Issue Type: New Feature Assignee: huybrechts Components: parameterized-trigger Created: 14/Jan/13 10:06 AM Description: Define an implicit parameter that restricts the downstream jobs to run on the same computer. This is an implicit parameter, so it wouldn't require the downstream jobs to be parameterized. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError Jenkins ver. 1.498 Duplicate Code Scanner Plug-in 2.33 It´s a freestyle project, building is done through windows batch files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
dogfood commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Integrated in jenkins_main_trunk #2186 [FIXED JENKINS-9679] integrated remoting 2.21 that contains the fix. (Revision 8a4bedd0df9b5d642945eb601ddb99bb75e87131) Result = UNSTABLE kohsuke : 8a4bedd0df9b5d642945eb601ddb99bb75e87131 Files : changelog.html pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16330) Trigger should start two jobs, but one is never started
Tomasz Wysocki updated JENKINS-16330 Trigger should start two jobs, but one is never started Installed plugins. Change By: Tomasz Wysocki (14/Jan/13 10:57 AM) Attachment: Selection_302.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
[JIRA] (JENKINS-16330) Trigger should start two jobs, but one is never started
Tomasz Wysocki commented on JENKINS-16330 Trigger should start two jobs, but one is never started I don't think that some of the users are removing tasks. I have attached installed plugins as png. Is there any log where I can check if task was removed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Sascha Vogt commented on JENKINS-15680 I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml' We're facing the same issue. It seems to be related to the Jenkins CVS plugin (after updating from 1.2 to 2.7 which was a change from the commandline cvs client to the Netbeans Java API). Comparing the output, it seems that now the plugin also uses "-r HEAD" for checkout / update: cvs q -z3 update -PdC -D "Friday, December 7, 2012 1:30:28 PM UTC" < old vs. cvs update d -P -r HEAD -D 14 Jan 2013 10:33:16 +0100 workspace < new Using the flag "Legacy Mode" changes the command to cvs update -P -N -D 14 Jan 2013 12:22:23 +0100 which seems to be a workaround. I had a look at the cvs documentation, and there it is stated that -D and -r are exclusive or (so I think the new command with specifiying both isn't quite correct) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Sascha Vogt edited a comment on JENKINS-15680 I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml' We're facing the same issue. It seems to be related to the Jenkins CVS plugin (after updating from 1.2 to 2.7 which was a change from the commandline cvs client to the Netbeans Java API). Comparing the output, it seems that now the plugin also uses "-r HEAD" for checkout / update: cvs q -z3 update -PdC -D "Friday, December 7, 2012 1:30:28 PM UTC" < old vs. cvs update d -P -r HEAD -D 14 Jan 2013 10:33:16 +0100 workspace < new Using the flag "Legacy Mode" changes the command to cvs update -P -N -D 14 Jan 2013 12:22:23 +0100 which seems to be a workaround. I had a look at the cvs documentation, and there it is stated that -D and -r are exclusive or (so I think the new command with specifiying both isn't quite correct) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Sascha Vogt edited a comment on JENKINS-15680 I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml' We're facing the same issue. It seems to be related to the Jenkins CVS plugin (after updating from 1.2 to 2.7 which was a change from the commandline cvs client to the Netbeans Java API). Comparing the output, it seems that now the plugin also uses "-r HEAD" for checkout / update: old cvs -q -z3 update -PdC -D "Friday, December 7, 2012 1:30:28 PM UTC" vs. new cvs update -d -P -r HEAD -D 14 Jan 2013 10:33:16 +0100 workspace Using the flag "Legacy Mode" changes the command to cvs update -P -N -D 14 Jan 2013 12:22:23 +0100 which seems to be a workaround. I had a look at the cvs documentation, and there it is stated that -D and -r are exclusive or (so I think the new command with specifiying both isn't quite correct) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Sascha Vogt updated JENKINS-15680 I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml' Change By: Sascha Vogt (14/Jan/13 12:10 PM) Environment: Windows Jenkins version 1.486 Linux Jenkins 1.480.2, cvs-plugin 2.7 Component/s: cvs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16335) Managed Script calls other managed script
Axel Heider created JENKINS-16335 Managed Script calls other managed script Issue Type: Improvement Affects Versions: current Assignee: domi Components: managed-scripts Created: 14/Jan/13 12:32 PM Description: Currently, one script can call another script when it knows its name. But there plugin does not know this and we must use the internal name of the script. I'm requestinga feature where the plugin is aware of one script calling the other script and thus a well define interface is provided here that can be used in the script. And the dependencies should be visible in the GUI. Writing this, I come to think of a even more generic plugin "meta-buidstep" or "post-buildstep" here. Where several jobs can use the same meta-step instead of defining all the smae steps in each jos over and over again. Project: Jenkins Priority: Minor Reporter: Axel Heider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Sergej Kleva commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Sorry for asking ... but how can i integrate that fix into my Jenkins ver. 1.498 ? Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
sogabe commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option All you have to do is updating your Jenkins to 1.499. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16330) Trigger should start two jobs, but one is never started
rsandell commented on JENKINS-16330 Trigger should start two jobs, but one is never started Nothing in that list that I can find either. Could it be triggered builds that are on the same patch set number? The queue consolidates runs that have the same exact parameters as another scheduled task. That could be the reason the run is "lost". We fixed that in 2.6.0 by introducing a unique hash parameter for every triggered build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Sergej Kleva commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Thanks! Greatly appreciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12117) Flickers (mostly on Chrome)
wernight resolved JENKINS-12117 as Cannot Reproduce Flickers (mostly on Chrome) Change By: wernight (14/Jan/13 1:00 PM) Status: Open Resolved 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
[JIRA] (JENKINS-12117) Flickers (mostly on Chrome)
wernight commented on JENKINS-12117 Flickers (mostly on Chrome) Seems not fickering anymore but it's difficult to tell the reason after all this time. Jenkins 1.480.1 Chrome 23 Firefox 18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError This is how I call simian: C:\Simian\bin\simian-2.3.33.exe -formatter=xml:%WORKSPACE%\simian.xml "C:\Jenkins\jobs\QiBuilder\workspace\QiBuilder**.c" "C:\Jenkins\jobs\QiBuilder\workspace\QiBuilder**.h" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Sergej Kleva commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Hi! I've updated to 1.499 but error is still there: -Xrs -jar "%BASE%\slave.jar" -jnlpUrl http://aaa.bbb.ccc:8080/computer/slave01/slave-agent.jnlp -classpath "%BASE%\commons-codec-1.7.jar" -jnlpCredentials xxx:yyy -noCertificateCheck Error: Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:229) at hudson.remoting.Launcher.run(Launcher.java:200) at hudson.remoting.Launcher.main(Launcher.java:173) Caused by: java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64 at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 3 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12065) Maven errors when job has "Build Selector for Copy Artifact"
peter_schuetze resolved JENKINS-12065 as Cannot Reproduce Maven errors when job has "Build Selector for Copy Artifact" seems to work now Change By: peter_schuetze (14/Jan/13 1:29 PM) Status: Open Resolved 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
[JIRA] (JENKINS-16044) Exception on CVS Log parsing
Anders Monrad
commented on JENKINS-16044
Exception on CVS Log parsing
This is due to us using CVSNT and a NT path in the CVSROOT. Our CVSROOT was :pserver:cvsuser@:d:\cvs, this caused line 142 in CvsLog to fail:
final String rootName = cvsRoot.split("/", 2)[1];
I guess this is expecting a regular unix like path like /cvs/repo/.
Changing our CVSROOT to forwardslash 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
[JIRA] (JENKINS-16336) Cyclic trigger relationship causes a script error
Kohsuke Kawaguchi created JENKINS-16336 Cyclic trigger relationship causes a script error Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 14/Jan/13 2:04 PM Description: This plugin isn't written to gracefully cope with dependency graph that contains a cycle in it. I encourage the plugin to cut the cycle by remembering jobs that were already traversed. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16337) SSH public key field in the user config page lacks form validation
Kohsuke Kawaguchi created JENKINS-16337 SSH public key field in the user config page lacks form validation Issue Type: Bug Assignee: Unassigned Components: ssh Created: 14/Jan/13 2:08 PM Description: It is a common mistake to type the SSH key in multiple lines. Look for these typical errors and make sure the keys follow the valid syntax. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16338) Jenkins fails to keep connection alive on Windows 8
Vassilena Treneva created JENKINS-16338 Jenkins fails to keep connection alive on Windows 8 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, slave-setup, slave-status Created: 14/Jan/13 2:52 PM Description: Launch slave agent via Java Web Start is the connection option. At some point of time, Jenkins fails to reach the slave. The error I see is: [java] Please wait while the installer processes files, 30 out of 39 modules done [java] FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy46.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.Ant.perform(Ant.java:217) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Master Jenkins: Linux bambpmsauto 2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux Jenkins ver. 1.497 Slave: Windows 8 Pro 64-bit edition Project: Jenkins Priority: Major Reporter: Vassilena Treneva This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16338) Jenkins fails to keep connection alive on Windows 8
Vassilena Treneva updated JENKINS-16338 Jenkins fails to keep connection alive on Windows 8 Change By: Vassilena Treneva (14/Jan/13 2:53 PM) Description: Launch slave agent via Java Web Start is the connection option.At some point of time, Jenkins fails to reach the slave. The error I see is:[java] Please wait while the installer processes files, 30 out of 39 modules done [java] FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closedhudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy46.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.Ant.perform(Ant.java:217) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) The last log entry under /var/lib/jenkins/logs/slaves/vmbam08.eur.ad.sag shows this:JNLP agent connected from /10.74.21.234<===[HUDSON REMOTING CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAAY= This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Ulli Hafner commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError I tried to reproduce that problem, but had no success so far. From the exception it is hard to see where it actually crashed. How big is the dry-warnings.xml file in the build folder on your machine? Can you try to lower the number of lines that identify a warning in simian? Just to see if the total number of warnings cause that 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
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Ulli Hafner commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError Here is my output, my filesize is 486 MByte... Gestartet durch Benutzer anonymous Building in workspace /Users/hafner/Development/jenkins/jobs/JENKINS-16298/workspace [DRY] Collecting duplicate code analysis files... [DRY] Finding all files that match the pattern **/simian.xml [DRY] Parsing 1 files in /Users/hafner/Development/jenkins/jobs/JENKINS-16298/workspace [DRY] Successfully parsed file /Users/hafner/Development/jenkins/jobs/JENKINS-16298/workspace/simian.xml of module with 10404 warnings. [DRY] Computing warning deltas based on reference build #2 Finished: SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15353) Missing descriptor exception in Jenkins log for Throttle Concurrent Builds plugin
Brent Duffy commented on JENKINS-15353 Missing descriptor exception in Jenkins log for Throttle Concurrent Builds plugin We're still seeing this exception on Jenkins 1.466.2 with Throttle Concurrent Builds plugin version 1.7.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
[JIRA] (JENKINS-16339) Jobname truncated in next-executions
mwebber created JENKINS-16339 Jobname truncated in next-executions Issue Type: Bug Assignee: Unassigned Attachments: next-execution.png Components: next-executions Created: 14/Jan/13 4:25 PM Description: The width of the "next executions" display is not sufficient to show the full name of my Jenkins jobs - see attached screenshot. I reduced the width of the date field, so that it just shows something like "Mon 16:21", but it did not help at all. If the datetime width is reduced, the jobname width should expand to use it. Also, I think it would look better if the datetime was on the left, and the jobname on the right. Thanks Project: Jenkins Priority: Major Reporter: mwebber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
SCM/JIRA link daemon commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/AbstractClearCaseScm.java src/main/java/hudson/plugins/clearcase/ClearCaseInstallation.java src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java src/main/java/hudson/plugins/clearcase/ClearToolExec.java src/main/java/hudson/plugins/clearcase/MkViewParameters.java src/main/java/hudson/plugins/clearcase/viewstorage/ColocatedViewStorage.java src/main/java/hudson/plugins/clearcase/viewstorage/ServerViewStorage.java src/main/java/hudson/plugins/clearcase/viewstorage/SpecificViewStorage.java src/main/java/hudson/plugins/clearcase/viewstorage/ViewStorage.java src/main/java/hudson/plugins/clearcase/viewstorage/ViewStorageDescriptor.java src/main/java/hudson/plugins/clearcase/viewstorage/ViewStorageFactory.java src/main/resources/hudson/plugins/clearcase/AbstractClearcaseScm/help-overrideViewStorage.html src/main/resources/hudson/plugins/clearcase/AbstractClearcaseScm/help-viewStorage.html src/main/resources/hudson/plugins/clearcase/ClearCaseInstallation/global.jelly src/main/resources/hudson/plugins/clearcase/ClearCaseSCM/config.jelly src/main/resources/hudson/plugins/clearcase/ClearCaseUcmSCM/config.jelly src/main/resources/hudson/plugins/clearcase/viewstorage/ServerViewStorage/config.jelly src/main/resources/hudson/plugins/clearcase/viewstorage/ServerViewStorage/help-assignedLabelString.html src/main/resources/hudson/plugins/clearcase/viewstorage/ServerViewStorage/help-server.html src/main/resources/hudson/plugins/clearcase/viewstorage/SpecificViewStorage/config.jelly src/main/resources/hudson/plugins/clearcase/viewstorage/ViewStorage/config.jelly src/test/java/hudson/plugins/clearcase/ClearCaseSCMDummy.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java src/test/java/hudson/plugins/clearcase/viewstorage/ColocatedViewStorageTest.java src/test/java/hudson/plugins/clearcase/viewstorage/ServerViewStorageTest.java src/test/java/hudson/plugins/clearcase/viewstorage/SpecificViewStorageTest.java http://jenkins-ci.org/commit/clearcase-plugin/eb8966a93ffeb4898d102e5cf0aa16d4556a0023 Log: JENKINS-16234 Fixed Clearcase Base support Re-implement ViewStorage support by defining an ExtensionPoint. Allows to define a default ViewStorage value in global settings, which can be overriden at job level. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12195) Any testReport with a # in the name creates broken links
Christian Höltje commented on JENKINS-12195 Any testReport with a # in the name creates broken links It works for now with versions: Jenkins ver. 1.480.1 xUnit Plugin ver. 1.51 Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12195) Any testReport with a # in the name creates broken links
Christian Höltje resolved JENKINS-12195 as Fixed Any testReport with a # in the name creates broken links Works now. Change By: Christian Höltje (14/Jan/13 4:49 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
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Vincent Latombe commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Steve, I just pushed a branch with the necessary changes to fix Base, I would be grateful if you could give it a try. You can download the hpi directly from https://buildhive.cloudbees.com/job/jenkinsci/job/clearcase-plugin/50/org.jenkins-ci.plugins$clearcase/artifact/org.jenkins-ci.plugins/clearcase/1.3.13-SNAPSHOT/clearcase-1.3.13-SNAPSHOT.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification The user ID will typically include underscores, but there ought to be a separate email property (shown at /user/*/configure) that includes the original email address. Perhaps this got broken by the recent split of the mailer plugin out of core; definitely assigning of emails to users who sign themselves up in the web UI was broken (fix will be in 1.500), but user creation from SCM changelogs is a different code path. Need to check if it is reproducible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9142) "Add Build Step" button broken in job configure page
Edward Griffin commented on JENKINS-9142 "Add Build Step" button broken in job configure page This problem is affecting me in Jenkins 1.464. I managed to work around it by using a chrome incognito window, so it probably does have to do with cookies. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15739) Add Execute Windows batch command to slave-setup plugin
Blaine Whited commented on JENKINS-15739 Add Execute Windows batch command to slave-setup plugin My organization (IXI Corporation/Equifax) are currently transitioning to a Jenkins CI system to help with deployments and box setup and configuration, to better support a swarm, and this plugin provides some very nice features to the system as a whole, I noticed this issue as well and started digging. I have created a potential fix to this error and I wanted some input. What I have discovered and done: Because of where the slave-setup injects itself into the slave start-up procedure, the OS of the slave doesn't seem to be available, no matter how I tried to retrieve it, the call you think might provide this value, is only available on the Master node, per the documentation. I currently have a patch that I am using in our production system that uses a slave label of windows (case-insensitive) to determine whether to launch the shell or batch object. Even with this change the plugin cannot be built on a windows box because of the echo command syntax in the unit test, but because of the way this unit test is preformed, I am able to query for the slave's OS and tweak the echo command accordingly to pass the test on windows (without effecting any-non windows builds) and allow for complete compilation and packaging. What I wanted to discuss: Would it be more desirable to automatically detect a Windows OS by try-catching the current plugin's process of starting the shell with the error it is expected to throw, automatically trying the batch alternative, and failing if neither are successful, as I don't want to force anyone to use labels they don't want. I could even have the system skip the try-catch if the user decided to add a Windows label, effectively implementing both solutions, and reducing memory usage by skipping the overhead of a try-catch block. Any input would be greatly appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16340) Can't watch any projects
T. Houdayer created JENKINS-16340 Can't watch any projects Issue Type: Bug Assignee: Unassigned Components: tracking-svn Created: 14/Jan/13 5:40 PM Description: I think it's not the best place to tell about this bug, but I can't add another Jenkins project in my watches list. I'm stuck with 4 projects. Is there a bug in the wiki.jenkins-ci.org system ? If yes this bug is here since many months. I'm using firefox 17, under Windows 7 x64. Project: Jenkins Priority: Minor Reporter: T. Houdayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74
commented on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Your compilation fix doesn't seem to work:
c:\git_repos\ivy-plugin\src\main\java\hudson\ivy\IvyBuild.java:503: inconvertible types
found : hudson.model.AbstractProject
required: hudson.ivy.IvyModule
env.put("IVY_MODULE_NAME", ((IvyModule) buildParent).getModuleName().name);
^
c:\git_repos\ivy-plugin\src\main\java\hudson\ivy\IvyBuild.java:504: inconvertible types
found : hudson.model.AbstractProject
required: hudson.ivy.IvyModule
env.put("IVY_MODULE_ORGANISATION", ((IvyModule) buildParent).getModuleName().organisation);
^
Note: c:\git_repos\ivy-plugin\src\main\java\hudson\ivy\IvyBuild.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Fatal error compiling
my environment:
$ java -version
java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing)
$ mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_14
Java home: c:\Program Files\Java\jdk1.6.0_14\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11727) Discard Unreadable Data - NPE
Samuel Webber
commented on JENKINS-11727
Discard Unreadable Data - NPE
I get the same error (with different discardable data) on the latest version 1.499.
I do have my Build Record Root Directory set to /workspace/jenkins/builds/${ITEM_FULLNAME} if that is of any relevance.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16326) TAP Parser can't handle SKIP_ALL
Todd Rinaldo edited a comment on JENKINS-16326 TAP Parser can't handle SKIP_ALL Good! in that case that's easier. Here's what the output looks like in that case: $>prove -wlvm t/00_devel_smoke_pl.t t/00_devel_smoke_pl.t .. 1..0 # SKIP Long-running tests disabled unless SLOW_TESTS environment variable set. skipped: Long-running tests disabled unless SLOW_TESTS environment variable set. Files=1, Tests=0, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.04 cusr 0.00 csys = 0.07 CPU) Result: NOTESTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16326) TAP Parser can't handle SKIP_ALL
Todd Rinaldo commented on JENKINS-16326 TAP Parser can't handle SKIP_ALL Good! in that case that's easier. Here's what theoutput looks like in that case: $>prove -wlvm t/00_devel_smoke_pl.t t/00_devel_smoke_pl.t .. 1..0 # SKIP Long-running tests disabled unless SLOW_TESTS environment variable set. skipped: Long-running tests disabled unless SLOW_TESTS environment variable set. Files=1, Tests=0, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.04 cusr 0.00 csys = 0.07 CPU) Result: NOTESTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
eguess74 commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type Could you please clarify your last comment? Also I believe you understood the problem correctly, but just to double check: Ivy build trigger has a setting to set where the ivy settings file is. This is used by all free style jobs that are using ivy build trigger. I would like to be able to specify the same thing for all builds of "ivy job" type on the server using absolute path to the ivy settings file commonly used by all projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16325) TAP Parser can't handle the output from prove
Todd Rinaldo commented on JENKINS-16325 TAP Parser can't handle the output from prove Sure this is really simple to produce. I apologize for my bad terminology in advance 1. Make a project called YAML-Syck 2. Track git source: git://github.com/toddr/YAML-Syck.git 3. Your build steps are: 3a. perl Makefile.PL 3b. make 3c. prove -wbvm t/*.t 2>&1 > $WORKSPACE/prove.tap 4. Add the TAP plugin to the Post-build Actions. Test results come from prove.tap This is my console output from running it: Started by user Todd Rinaldo Building in workspace /var/lib/jenkins/workspace/YAML-Syck Checkout:YAML-Syck / /var/lib/jenkins/workspace/YAML-Syck - hudson.remoting.LocalChannel@1dc2b19 Using strategy: Default Fetching changes from 1 remote Git repository Fetching upstream changes from git://github.com/toddr/YAML-Syck.git Seen branch in repository origin/HEAD Seen branch in repository origin/historical/git-svn-conversion Seen branch in repository origin/master Seen branch in repository origin/tmp Commencing build of Revision 9708eff55268b905a9edd5fa4cb51337f8646430 (origin/historical/git-svn-conversion) Checking out Revision 9708eff55268b905a9edd5fa4cb51337f8646430 (origin/historical/git-svn-conversion) No change to record in branch origin/historical/git-svn-conversion [YAML-Syck] $ /bin/sh -xe /tmp/hudson5181651939588478127.sh + perl Makefile.PL *** WARNING *** YAML::Syck version >=0.60 breaks compatibility with earlier versions of YAML::Syck and YAML.pm (<0.60) when serializing blessed references. See the COMPATIBILITY file for more information. Writing Makefile for YAML::Syck Writing MYMETA.yml and MYMETA.json [YAML-Syck] $ /bin/sh -xe /tmp/hudson4366761815976251983.sh + make cp lib/JSON/Syck.pm blib/lib/JSON/Syck.pm cp lib/YAML/Loader/Syck.pm blib/lib/YAML/Loader/Syck.pm cp lib/YAML/Dumper/Syck.pm blib/lib/YAML/Dumper/Syck.pm cp lib/YAML/Syck.pm blib/lib/YAML/Syck.pm /usr/bin/gcc -c -I. -I/usr/local/cpanel/3rdparty/perl/514/include -L/usr/local/cpanel/3rdparty/perl/514/lib -I/usr/local/cpanel/3rdparty/include -L/usr/local/cpanel/3rdparty/lib -DAPPLLIB_EXP="/usr/local/cpanel" -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -DVERSION=\"1.04\" -DXS_VERSION=\"1.04\" -fPIC "-I/usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.3/i386-linux-64int/CORE" bytecode.c /usr/bin/gcc -c -I. -I/usr/local/cpanel/3rdparty/perl/514/include -L/usr/local/cpanel/3rdparty/perl/514/lib -I/usr/local/cpanel/3rdparty/include -L/usr/local/cpanel/3rdparty/lib -DAPPLLIB_EXP="/usr/local/cpanel" -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -DVERSION=\"1.04\" -DXS_VERSION=\"1.04\" -fPIC "-I/usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.3/i386-linux-64int/CORE" emitter.c /usr/bin/gcc -c -I. -I/usr/local/cpanel/3rdparty/perl/514/include -L/usr/local/cpanel/3rdparty/perl/514/lib -I/usr/local/cpanel/3rdparty/include -L/usr/local/cpanel/3rdparty/lib -DAPPLLIB_EXP="/usr/local/cpanel" -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -DVERSION=\"1.04\" -DXS_VERSION=\"1.04\" -fPIC "-I/usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.3/i386-linux-64int/CORE" gram.c /usr/bin/gcc -c -I. -I/usr/local/cpanel/3rdparty/perl/514/include -L/usr/local/cpanel/3rdparty/perl/514/lib -I/usr/local/cpanel/3rdparty/include -L/usr/local/cpanel/3rdparty/lib -DAPPLLIB_EXP="/usr/local/cpanel" -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -DVERSION=\"1.04\" -DXS_VERSION=\"1.04\" -fPIC "-I/usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.3/i386-linux-64int/CORE" handler.c /usr/bin/gcc -c -I. -I/usr/local/cpanel/3rdparty/perl/514/include -L/usr/local/cpanel/3rdparty/perl/514/lib -I/usr/local/cpanel/3rdparty/include -L/usr/local/cpanel/3rdparty/lib -DAPPLLIB_EXP="/usr/local/cpanel" -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -DVERSION=\"1.04\" -DXS_VERSION=\"1.04\" -fPIC "-I/usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.3/i386-linux-64int/CORE" implicit.c /usr/bin/gcc -c -I. -I/usr/local/cpanel/3rdparty/perl/514/include -L/usr/local/cpanel/3rdparty/perl/514/lib -I/usr/local/cpanel/3rdparty/include -L/usr/local/cpanel/3rdparty/lib -DAPPLLIB_EXP="/usr/local/cpanel" -fno-strict-aliasing -pipe -fstack-protector -I/usr/loc
[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification In my case the user's don't sign up themselves, they don't have Jenkins accounts. Emails are extracted from SCM log only. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification In my case the user's don't sign up themselves, they don't have Jenkins accounts and cannot login into Jenkins. Emails are extracted from SCM log only. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Sergey Grigoriev edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification In my case the commiters don't sign up themselves, they don't have Jenkins accounts and cannot login into Jenkins. Emails are extracted from SCM log only. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16325) TAP Parser can't handle the output from prove
Todd Rinaldo commented on JENKINS-16325 TAP Parser can't handle the output from prove Right now my work around is NASTY. Instead of prove, I can do: mkdir -p $WORKSPACE/t; for test in t/*.t; do; prove -wlvm $test > $WORKSPACE/$test 2>&1; done Of course I'm still being bitten by JENKINS-16326 ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15472) Option to create a new page
Vince Yap commented on JENKINS-15472 Option to create a new page Thanks for implementing this. Any ETA on 1.8? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74 commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used As for the main problem, i "greped" the jenkins log: Every job has the an entry in the jenkins log file Configured Ivy using custom settings path/to/our_global_ivy_settings_file.xml I have found NO entries for the lines: Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15472) Option to create a new page
Joe Hansche closed JENKINS-15472 as Fixed Option to create a new page Sorry for the delay. 1.8 was just released to the update center. Change By: Joe Hansche (14/Jan/13 7:08 PM) 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
[JIRA] (JENKINS-10266) Set grails.work.dir to something unique by default
candrews commented on JENKINS-10266 Set grails.work.dir to something unique by default It is definitely still an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5413) SCM polling getting hung
lacostej updated JENKINS-5413 SCM polling getting hung I encountered a very similar issue, yet I have a slightly different setup: 1 master 1 slave yet the polling was stuck on the master only SCM polling hanging (warning displayed in Jenkins configure screen). Oldest hanging thread is more than 2 days old. it seems it all started with a Unix process that in some way never returned: ps -aef| grep jenkins 300 12707 1 0 26Nov12 ?? 1336:33.09 /usr/bin/java -Xmx1024M -XX:MaxPermSize=128M -jar /Applications/Jenkins/jenkins.war 300 98690 12707 0 Sat03PM ?? 0:00.00 git fetch -t https://github.com/jenkinsci/testflight-plugin.git +refs/heads/*:refs/remotes/origin/* 300 98692 98690 0 Sat03PM ?? 4:39.72 git-remote-https https://github.com/jenkinsci/testflight-plugin.git https://github.com/jenkinsci/testflight-plugin.git 0 3371 3360 0 8:20PM ttys0000:00.02 su jenkins 300 4017 3372 0 8:52PM ttys0000:00.00 grep jenkins 0 10920 10896 0 19Nov12 ttys0010:00.03 login -pfl jenkins /bin/bash -c exec -la bash /bin/bash Running Jenkins 1.479 I killed the processes and associated threads, and it started being better. Polling doesn't enfore timeouts ? Change By: lacostej (14/Jan/13 8:15 PM) Attachment: DUMP1.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured
Eric Smalling commented on JENKINS-12547 ec2-plugin doesn't allow for multiple EC2 clouds to be configured I think I am running into the same problem - has anyone found a work-around 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
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
Jesse Glick created JENKINS-16341 Memory leak in createJavaScriptProxy Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Jan/13 8:39 PM Description: Never seems to release bound objects, even after they have been rendered. Project: Jenkins Labels: stapler Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7683) "Restrict where this project can be run"-Option not available for Matrix builds
Don Ross commented on JENKINS-7683 "Restrict where this project can be run"-Option not available for Matrix builds I am encountering this same problem; however, it is not the parent job that it is the problem, it is that all of my matrix jobs are running on the master when I want them to run on specific slaves. On other jobs, I set the 'Restrict where this project can be run' to "NODE1 | NODE2 | NODE3" (etc), and the job runs on whichever system is available. When setting up a matrix job, I see no way to do this except to create an additional axis. But, if I do that, then I get a two-dimensional matrix, and each of my configurations runs once on each host. What am I supposed to do in this situation? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
Jesse Glick commented on JENKINS-16341 Memory leak in createJavaScriptProxy In Jenkins Enterprise, merely opening the config page for a newly created freestyle job results in >100 RenderOnDemandClosure instances being bound, none of which are ever released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7683) "Restrict where this project can be run"-Option not available for Matrix builds
kbertelson commented on JENKINS-7683 "Restrict where this project can be run"-Option not available for Matrix builds Take a look at the "Combination Filter" feature of a matrix project. The help text tells you how to fine-tune which configurations to run on which host. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Jim Yanko commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Went to: Manage Jenkins/Configure System/Extended E-mail Notification I set the override settings for Extended Email Notify as follows... [x] Override Global Settings SMTP server [ localhost] Default user E-mail suffix [ hostname.env.domain.com ] System Admin E-mail Address [ us...@hostname.env.domain.com ] Notably, I set the override to use a diff acct name for the email address from the default by adding the '2' so I could confirm the override setting was being used to send the email. With Jenkins 1.493 (and email ext v 2.25) Ran a few builds of the sample job to force failure and success. Got emails from user2 address for each (indicates the override setting worked) Upgraded Jenkins to 1.498 (and email ext v 2.25) Ran a few builds of the sample job to force failure and success. each that should have sent email failed to send message for the status change ERROR: Could not send email as a part of the post-build publishers. Rolling back Jenkins to 1.493 (and email ext v 2.25) Ran a few builds of the sample job to force failure and success. Got emails from user2 address for each (indicates the override setting worked) Following is from the console log from the forced failure condition with Jenkins 1.498 installed... ... Starting the test @ Mon Jan 14 20:33:47 UTC 2013 (1358195627471) Waiting for possible shutdown message on port 4445 Tidying up ...@ Mon Jan 14 20:33:51 UTC 2013 (1358195631145) ... end of run Performance: Percentage of errors greater or equal than 5% sets the build as unstable Performance: Percentage of errors greater or equal than 10% sets the build as failure Performance: Recording JMeter reports '*.jtl' Performance: Parsing JMeter report file results.jtl Performance: File results.jtl reported 60.0% of errors [FAILURE]. Build status is: FAILURE Build step 'Publish Performance test result report' changed build result to FAILURE Recording fingerprints IRC notifier plugin: Sending notification to: #alerts Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: First Failure Trigger Success was overridden by another trigger and will not send an email. Sending email for trigger: First Failure Overriding default server settings, creating our own session ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:439) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1587) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Some error occured trying to send the email...check the Jenkins log Finished: FAILURE Just realized that I am seeing the following message each time I get back to version 1.493 when I go to the Manage Jenkins page. Is this significant to the issue at hand? Manage Jenkins You have data stored in an older format and/or unreadable data. New version of Jenkins (1.498) is available for download (changelog). Or Upgrade Automatically If I follow the manage link, it basically only gives me an option to 'discard unreadable data' and nothing else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Ok, it looks like that is the line that is trying to get the charset from Mailer...that will have to be updated. I'll try and release a 2.26 ASAP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6203) Git plugin uses default encoding to read change log file
evernat commented on JENKINS-6203 Git plugin uses default encoding to read change log file Perhaps, fixed by this pull request: https://github.com/jenkinsci/git-plugin/pull/98 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12179) The commit subject lines are garbled in the changelog
evernat commented on JENKINS-12179 The commit subject lines are garbled in the changelog And perhaps, fixed by this pull request: https://github.com/jenkinsci/git-plugin/pull/98 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
evernat resolved JENKINS-4861 as Cannot Reproduce Post-build deployment of Maven artifacts does not work with scpexe-type repository So resolving as "can not reproduce". Anyone, please reopen if reproduced. Change By: evernat (14/Jan/13 10:00 PM) Status: Open Resolved 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
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base No good. [DemoWestBuild_JanRVL] $ /usr/atria/bin/cleartool mkview -snapshot -tag DevJenkins_z565250_DevBuild_DemoWestBuild_JanRVL -stgloc -auto DevJenkins_z565250_DevBuild_DemoWestBuild_JanRVL cleartool: Error: No available Server Storage Location entries. FATAL: Base ClearCase failed. exit code=1 java.io.IOException: cleartool did not return the expected exit code. Command line="mkview -snapshot -tag DevJenkins_z565250_DevBuild_DemoWestBuild_JanRVL -stgloc -auto DevJenkins_z565250_DevBuild_DemoWestBuild_JanRVL", actual exit code=1 at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:121) at hudson.plugins.clearcase.ClearToolExec.mkview(ClearToolExec.java:657) at hudson.plugins.clearcase.action.SnapshotCheckoutAction.cleanAndCreateViewIfNeeded(SnapshotCheckoutAction.java:163) at hudson.plugins.clearcase.action.BaseSnapshotCheckoutAction.checkout(BaseSnapshotCheckoutAction.java:53) at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:656) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Sending e-mails to: ** Finished: FAILURE We don't have storage locations defined, so using stgloc doesn't work. No shared drives either, so no -vws capability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12038) Jenkins installs 32 bit JRE on Windows 2008 64 bit (the JRE in the JENKINS_HOME)
evernat commented on JENKINS-12038 Jenkins installs 32 bit JRE on Windows 2008 64 bit (the JRE in the JENKINS_HOME) 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
[JIRA] (JENKINS-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured
Eric Smalling assigned JENKINS-12547 to Eric Smalling ec2-plugin doesn't allow for multiple EC2 clouds to be configured Change By: Eric Smalling (14/Jan/13 10:24 PM) Assignee: Kohsuke Kawaguchi Eric Smalling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured
Eric Smalling commented on JENKINS-12547 ec2-plugin doesn't allow for multiple EC2 clouds to be configured Have what I believe to be a fix - will push to my fork in a minute. Will be doing some more testing from our server tomorrow before issuing the 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
[JIRA] (JENKINS-11871) Cannot access data in dropdownDescriptorSelector for validation
evernat commented on JENKINS-11871 Cannot access data in dropdownDescriptorSelector for validation 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
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Vincent Latombe commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Try using the new 'colocated view' location. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base Btw, in ClearCaseScmDescriptor.newInstance, there are several scenarios in the Job Configuration form involving Base Clearcase where no viewStorage fields get filled in, resulting in a NULL Reference for the ViewStorage object and therefore associated handling of a null ViewStorage. This is what was causing the '-stgloc -auto' to get created down the line, which is not appropriate when no Storage Locations have been defined by a Clearcase Admin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10007) Rebuild plugin does not work with Validating String Parameter Plugin
evernat resolved JENKINS-10007 as Duplicate Rebuild plugin does not work with Validating String Parameter Plugin Change By: evernat (14/Jan/13 10:34 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
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson commented on JENKINS-16234 Plugin does not currently work for Clearcase Base So far as I can tell, we don't have colocated views – which is what's probably messing up the default code plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11932) Git plugin NPE when building on Linux slave (sporadic)
evernat resolved JENKINS-11932 as Won't Fix Git plugin NPE when building on Linux slave (sporadic) I suppose that everyone has used the workaround now, and so there is no issue anymore. Change By: evernat (14/Jan/13 10:42 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson edited a comment on JENKINS-16234 Plugin does not currently work for Clearcase Base No good. [DemoWestBuild_JanRVL] $ /usr/atria/bin/cleartool mkview -snapshot -tag DevJenkins_DevBuild_DemoWestBuild_JanRVL -stgloc -auto DevJenkins_DevBuild_DemoWestBuild_JanRVL cleartool: Error: No available Server Storage Location entries. FATAL: Base ClearCase failed. exit code=1 java.io.IOException: cleartool did not return the expected exit code. Command line="mkview -snapshot -tag DevJenkins_DevBuild_DemoWestBuild_JanRVL -stgloc -auto DevJenkins_DevBuild_DemoWestBuild_JanRVL", actual exit code=1 at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:121) at hudson.plugins.clearcase.ClearToolExec.mkview(ClearToolExec.java:657) at hudson.plugins.clearcase.action.SnapshotCheckoutAction.cleanAndCreateViewIfNeeded(SnapshotCheckoutAction.java:163) at hudson.plugins.clearcase.action.BaseSnapshotCheckoutAction.checkout(BaseSnapshotCheckoutAction.java:53) at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:656) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Sending e-mails to: ** Finished: FAILURE We don't have storage locations defined, so using stgloc doesn't work. No shared drives either, so no -vws capability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11936) Slave hang for a long time when a job is completes
evernat commented on JENKINS-11936 Slave hang for a long time when a job is completes 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
[JIRA] (JENKINS-16234) Plugin does not currently work for Clearcase Base
Steve Davidson edited a comment on JENKINS-16234 Plugin does not currently work for Clearcase Base So far as I can tell, we don't have colocated views – which is what's probably messing up the default code in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11696) jenkins commandline version list-changes command PLAIN CSV format doesnot produce desired result
evernat commented on JENKINS-11696 jenkins commandline version list-changes command PLAIN CSV format doesnot produce desired result I do not understand what is the issue. What is the current result and what is expected? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured
Eric Smalling started work on JENKINS-12547 ec2-plugin doesn't allow for multiple EC2 clouds to be configured Change By: Eric Smalling (14/Jan/13 10:58 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
[JIRA] (JENKINS-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured
Eric Smalling commented on JENKINS-12547 ec2-plugin doesn't allow for multiple EC2 clouds to be configured My commit: https://github.com/ericsmalling/ec2-plugin/commit/15d2c00e247ed54bace3c5cacb5e7ae0022a1f87 has the changes I intend on issuing the pull req from (in case you want to review before I finish testing) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12012) "Atomatic upgrade" link is no longer available on Manage Jenkins Page
evernat commented on JENKINS-12012 "Atomatic upgrade" link is no longer available on Manage Jenkins Page I do not reproduce the issue. Do you reproduce the issue 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Jim Yanko commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Allrighty - I'll keep my eyes open for it :-D This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
Jesse Glick
updated JENKINS-16341
Memory leak in createJavaScriptProxy
Heap delta in OSS trunk, after ~18 requests from {{curl -I http://localhost:8080/job/x/configure}}.
Change By:
Jesse Glick
(14/Jan/13 11:05 PM)
Attachment:
JENKINS-16341.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
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used So you have Java 1.6.0_37 installed but Maven is using Java 1.6.0_14. Is your JAVA_HOME environment variable correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16342) asynchPeople very slow when using Gravatar & Subversion plugins
Jesse Glick created JENKINS-16342 asynchPeople very slow when using Gravatar & Subversion plugins Issue Type: Bug Assignee: Jesse Glick Components: core, gravatar, subversion Created: 14/Jan/13 11:51 PM Description: https://gist.github.com/4534378 shows https://jenkins.ci.cloudbees.com/job/libraries/asynchPeople/ taking an inordinate amount of time in the callback. Clearly AsynchPeople.data() cannot assume that UserAvatarResolver.resolve is quick. UserGravatarResolver sometimes blocks on an HTTP connection to a web service, though this is cached. However every time it checks Mailer.UserProperty.getAddress, which in the presence of SubversionMailAddressResolverImpl examines every build of every project in every folder in all of Jenkins. This is so inefficient we probably never want to do it, much less synchronously in an HTTP request. Besides People, the avatar is used in a couple of per-User pages, which is perhaps OK; but shown for every User in the HudsonPrivateSecurityRealm overview, which is definitely not OK. Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used So you have Java 1.6.0_37 installed but Maven is using Java 1.6.0_14. Is your JAVA_HOME environment variable correct? Regardless I have added the Object workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
Johno Crawford commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type Feel free to try the snapshot which contains the changes ( https://issues.jenkins-ci.org/secure/attachment/23049/ivy.hpi ). As for my last comment, the path which is set in system configuration is the path which will be loaded from the slave ie. the ivy settings file must be present on the slave. Is this the desired behaviour? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11030) Deploying to Glassfish fails with a ClassCastException
Rob Weaver commented on JENKINS-11030 Deploying to Glassfish fails with a ClassCastException I have the same issue: channel stopped Deploying /usr/local/jenkins/workspace/OmnisTools/OmnisMaven/target/OmnisTools-1.0-SNAPSHOT.war to container GlassFish 3.x Remote ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.util.CargoException: Cannot communicate with the server at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:126) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:946) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: javax.enterprise.deploy.spi.exceptions.TargetException: Error getting required modules at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:313) at org.glassfish.deployapi.SunDeploymentManager.getRunningModules(SunDeploymentManager.java:200) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.findTargetModule(AbstractJsr88Deployer.java:350) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:122) ... 16 more Caused by: java.lang.ClassCastException: org.glassfish.deployapi.TargetImpl cannot be cast to org.glassfish.deployapi.TargetImpl at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:300) ... 19 more javax.enterprise.deploy.spi.exceptions.TargetException: Error getting required modules at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:313) at org.glassfish.deployapi.SunDeploymentManager.getRunningModules(SunDeploymentManager.java:200) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.findTargetModule(AbstractJsr88Deployer.java:350) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:122) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:946) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.lang.ClassCastException: org.glassfish.deployapi.TargetImpl cannot be cast to org.glassfish.deployapi.TargetImpl at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:300) ... 19 more Finished: FAILURE
[JIRA] (JENKINS-11030) Deploying to Glassfish fails with a ClassCastException
Rob Weaver commented on JENKINS-11030 Deploying to Glassfish fails with a ClassCastException BTW, same module deploys just fine from NetBeans remotely, GlassFish Admin page, or command line asadmin, so I'm guessing it has something to do with Jenkins not having access to some library in the GF classpath. Jenkins is running on the same GF where I'm trying to deploy this module. Have tried it both with the module already deployed and undeployed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Johno Crawford (15/Jan/13 12:39 AM) Attachment: ivy.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Would you please try the latest snapshot ( https://issues.jenkins-ci.org/secure/attachment/23055/ivy.hpi ). I have added logging to spit out the Java home and changed IvyXmlParser to load EnvVars. Changeset available at https://github.com/jenkinsci/ivy-plugin/commit/cdf08c9adde721f5ad93b9d0e79f4c0c013c4e0d.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11030) Deploying to Glassfish fails with a ClassCastException
Rob Weaver edited a comment on JENKINS-11030 Deploying to Glassfish fails with a ClassCastException BTW, same module deploys just fine from NetBeans remotely, GlassFish Admin page, or command line asadmin, so I'm guessing it has something to do with Jenkins not having access to some library in the GF classpath. Jenkins is running on the same GF where I'm trying to deploy this module. Have tried it both with the module already deployed and undeployed. Both on the job console and Jenkins log, I see the same exception: INFO: OmnisTools #19 main build action completed: SUCCESS WARNING: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.util.CargoException: Cannot communicate with the server at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:126) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:946) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: javax.enterprise.deploy.spi.exceptions.TargetException: Error getting required modules at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:313) at org.glassfish.deployapi.SunDeploymentManager.getRunningModules(SunDeploymentManager.java:200) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.findTargetModule(AbstractJsr88Deployer.java:350) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:122) ... 16 more Caused by: java.lang.ClassCastException: org.glassfish.deployapi.TargetImpl cannot be cast to org.glassfish.deployapi.TargetImpl at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:300) ... 19 more javax.enterprise.deploy.spi.exceptions.TargetException: Error getting required modules at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:313) at org.glassfish.deployapi.SunDeploymentManager.getRunningModules(SunDeploymentManager.java:200) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.findTargetModule(AbstractJsr88Deployer.java:350) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:122) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:946) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
SCM/JIRA link daemon commented on JENKINS-16341 Memory leak in createJavaScriptProxy Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/widgets/RenderOnDemandClosure.java http://jenkins-ci.org/commit/jenkins/08efdf5d3ab962cfd4c4c489266592fe1db7df8e Log: JENKINS-16341 Amelioration of memory leak by at least interning some heavily redundant strings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
Jesse Glick edited a comment on JENKINS-16341 Memory leak in createJavaScriptProxy Heap delta in OSS trunk, after ~18 requests from curl -I http://localhost:8080/job/x/configure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
Jesse Glick edited a comment on JENKINS-16341 Memory leak in createJavaScriptProxy Heap delta in OSS trunk, after ~18 requests from curl -I http://localhost:8080/job/x/configure >&- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16341) Memory leak in createJavaScriptProxy
dogfood commented on JENKINS-16341 Memory leak in createJavaScriptProxy Integrated in jenkins_main_trunk #2190 JENKINS-16341 Amelioration of memory leak by at least interning some heavily redundant strings. (Revision 08efdf5d3ab962cfd4c4c489266592fe1db7df8e) Result = SUCCESS Jesse Glick : 08efdf5d3ab962cfd4c4c489266592fe1db7df8e Files : changelog.html core/src/main/java/hudson/widgets/RenderOnDemandClosure.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12761) tfs plugin :failed to record scm polling
Jun Chen reopened JENKINS-12761 tfs plugin :failed to record scm polling The fix is not included in the latest public version of tfs plugin (v1.20) Change By: Jun Chen (15/Jan/13 4:52 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
K Ningthouj created JENKINS-16343 Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: error-msg.txt Components: subversion Created: 15/Jan/13 6:00 AM Description: We have 1.499 version of Jenkins installed along with 1.44 Subversion plugin. Though the correct credentials of Subversion repo were entered and accepted (Username/password authentication), while running the job it fails with the "E200015: No credential to try. Authentication failed" message. We have not been able to find a solution for this. We are getting this error message for all versions of Jenkins after 1.34 Please help in fixing this issue. Environment: O/S: Windows 7. Jenkins is installed as a windows service. Project: Jenkins Labels: jenkins plugin subversion Priority: Major Reporter: K Ningthouj This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
