[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Mikko Mattila commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I'm seeing this same issue with Jenkins 1.454 & the EnvInject plugin 1.74-SNAPSHOT from yesterday. I had 1.72 when I initially encountered this. Not reopening the bug yet, because I have no further useful information. This message is automatically generated by JIRA. 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-14551) an update which contains added files merged from a branch results in those files having doubled content
Patrick Streicher commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content Same issue: Jenkins 1.487, Jenkins Subversion Plug-in 1.43 This message is automatically generated by JIRA. 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-15499) HistoryWidget/entry.jelly throws NullPointerException
Patanachai Tangchaisin commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException The error is still there in 1.488 This message is automatically generated by JIRA. 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-15679) NPE when expanding more entries in build history
Patanachai Tangchaisin closed JENKINS-15679 as Duplicate NPE when expanding more entries in build history Thank you for reporting. Duplicate of JENKINS-15499 Change By: Patanachai Tangchaisin (06/Nov/12 7:24 AM) Status: Open Closed 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-15156) Builds Disappear from Build History after Completion
Tomas Hellberg commented on JENKINS-15156 Builds Disappear from Build History after Completion 12 hours later the history is back. This time without a master restart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15729) Please allow multiple sound output options
Mark Ribau created JENKINS-15729 Please allow multiple sound output options Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: sounds Created: 06/Nov/12 3:49 AM Description: Please allow choosing multiple sound output options via check boxes instead of radio boxes. For example, I'd like to play a sound on the local hardware when the build fails, but if people have any Jenkins page open, I'd like to also play the sound for them through their HTML5 browser. Project: Jenkins Priority: Minor Reporter: Mark Ribau This message is automatically generated by JIRA. 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-15719) Builds and workspace disappear for jobs created after upgrade to 1.487
vijay singh commented on JENKINS-15719 Builds and workspace disappear for jobs created after upgrade to 1.487 Krzysztof - Thanks for logging it on my behalf. This message is automatically generated by JIRA. 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-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Gregory Boissinot updated JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 Change By: Gregory Boissinot (05/Nov/12 10:20 PM) Component/s: core Component/s: envinject This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Brian Freed commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 Unfortunately my jobs are still disappearing with 1.489 with the CVS plugin disabled This message is automatically generated by JIRA. 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-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Margaret Lewicka commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed A very unfortunate bug indeed, especially if one of the batch of jobs getting launched gets stuck for whatever reasons (remote execution over ssh, etc.). The stuck job will cause the whole batch to get stuck, and the possibility of this happening is exactly why we're using concurrent executions in first place... This message is automatically generated by JIRA. 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-15728) Remote slave with Maven Repo Cleaner enabled as post build task fails.
Larry Shatzer, Jr. created JENKINS-15728 Remote slave with Maven Repo Cleaner enabled as post build task fails. Issue Type: Bug Assignee: Unassigned Components: maven-repo-cleaner Created: 05/Nov/12 9:57 PM Description: The slave is a remote linux server (host is linux too, although differing distros). It is connected to via SSH. I got this stacktrace in my build output: 14:50:30 Deleting old workspace snapshot from #440. 14:50:30 ERROR: Publisher org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerPostBuildTask aborted due to exception 14:50:30 hudson.util.IOException2: remote file operation failed: /home/jenkins/workspace/jobname/.repository at hudson.remoting.Channel@2a1f0c81:slavename 14:50:30 at hudson.FilePath.act(FilePath.java:847) 14:50:30 at hudson.FilePath.act(FilePath.java:824) 14:50:30 at org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerPostBuildTask.perform(MavenRepoCleanerPostBuildTask.java:44) 14:50:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 14:50:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 14:50:30 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779) 14:50:30 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994) 14:50:30 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) 14:50:30 at hudson.model.Run.execute(Run.java:1541) 14:50:30 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) 14:50:30 at hudson.model.ResourceController.execute(ResourceController.java:88) 14:50:30 at hudson.model.Executor.run(Executor.java:236) 14:50:30 Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4d0b24be 14:50:30 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) 14:50:30 at hudson.remoting.UserRequest.(UserRequest.java:62) 14:50:30 at hudson.remoting.Channel.call(Channel.java:663) 14:50:30 at hudson.FilePath.act(FilePath.java:840) 14:50:30 ... 11 more 14:50:30 Caused by: java.io.NotSerializableException: org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerPostBuildTask 14:50:30 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) 14:50:30 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 14:50:30 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 14:50:30 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 14:50:30 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 14:50:30 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) 14:50:30 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) 14:50:30 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) 14:50:30 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) 14:50:30 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) 14:50:30 at hudson.remoting.UserRequest._serialize(UserRequest.java:155) 14:50:30 at hudson.remoting.UserRequest.serialize(UserRequest.java:164) 14:50:30 ... 14 more Project: Jenkins Priority: Major Reporter: Larry Shatzer, Jr. This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Andre Kelpe commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 I don't want to make this into a cargo cult problem, but after I disabled the CVS plugin and restarted jenkins, it was gone. I don't know if it is related or not, but so far everything works as expected. YMMV. This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Brian Freed updated JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 Change By: Brian Freed (05/Nov/12 9:49 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Brian Freed commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 Can I get some traction on this issue? I am still not able to upgrade to anything above 1.484 This message is automatically generated by JIRA. 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-15727) JClouds Plug-In failing to start slave
abayer commented on JENKINS-15727 JClouds Plug-In failing to start slave Any chance you could get on the instance after that happens and see what shows up in /var/log/secure, say? This message is automatically generated by JIRA. 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-14188) shiningpanda python plugin doesn't allow choosing name of python executable
Olivier Mansion resolved JENKINS-14188 as Fixed shiningpanda python plugin doesn't allow choosing name of python executable This will be fixed in 0.15. You can now set the path to the Python executable in the "Home" field. Change By: Olivier Mansion (05/Nov/12 9:32 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-15727) JClouds Plug-In failing to start slave
Nathan Sharp created JENKINS-15727 JClouds Plug-In failing to start slave Issue Type: Bug Assignee: abayer Components: jclouds Created: 05/Nov/12 9:32 PM Description: I had trouble using the base Ubuntu 12.04 image on Amazon (ami-3d4ff254), so I've been making my own ami based on it that has Java and the build tools I need pre-installed. I have configured JClouds with "Use Pre-existing user" and "Use Pre-installed Java". The plug-in starts the machine, connects to it, then I get: [#|2012-11-05T16:12:48.801-0500|WARNING|oracle-glassfish3.1.1|hudson.slaves.NodeProvisioner|_ThreadID=26;_ThreadName=Thread-2;|Provisioned slave testaws failed to launch java.util.concurrent.ExecutionException: java.io.IOException: Error during SCP transfer. at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:227) at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:213) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Error during SCP transfer. at com.trilead.ssh2.SCPClient.put(SCPClient.java:510) at com.trilead.ssh2.SCPClient.put(SCPClient.java:466) at jenkins.plugins.jclouds.compute.JCloudsLauncher.launch(JCloudsLauncher.java:71) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) ... 5 more Caused by: java.io.IOException: Remote scp sent illegal error code. at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:53) at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:137) at com.trilead.ssh2.SCPClient.put(SCPClient.java:506) ... 8 more #] The failing line (JCloudsLauncher:71) appears to be trying to copy Slave.jar to /tmp on the node. I can manually scp this file and the manual scp succeeds. Any ideas on how to debug this? Environment: Jenkins 1.466.2, JClouds Plug-In 2.3.1, Ubuntu 12.04 x64. Connecting to Amazon EC2 trying to run an Ubuntu 12.04 image Project: Jenkins Priority: Blocker Reporter: Nathan Sharp This message is automatically generated by JIRA. 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-14262) Cannot tell what part of copyartifact plugin failed when optional is unchecked.
SCM/JIRA link daemon resolved JENKINS-14262 as Fixed Cannot tell what part of copyartifact plugin failed when optional is unchecked. Change By: SCM/JIRA link daemon (05/Nov/12 9:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14262) Cannot tell what part of copyartifact plugin failed when optional is unchecked.
SCM/JIRA link daemon commented on JENKINS-14262 Cannot tell what part of copyartifact plugin failed when optional is unchecked. Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/resources/hudson/plugins/copyartifact/Messages.properties http://jenkins-ci.org/commit/copyartifact-plugin/5826a3dcf2325dd4ee19e727b6568a90de327f1b Log: [FIXED JENKINS-14262] Add more diagnostic detail to failure message. Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/1f5a45c15aac...5826a3dcf232 This message is automatically generated by JIRA. 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-15726) PosixException thrown while changing file mode
SCM/JIRA link daemon resolved JENKINS-15726 as Fixed PosixException thrown while changing file mode Change By: SCM/JIRA link daemon (05/Nov/12 9:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15726) PosixException thrown while changing file mode
SCM/JIRA link daemon commented on JENKINS-15726 PosixException thrown while changing file mode Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/copyartifact/FingerprintingCopyMethod.java http://jenkins-ci.org/commit/copyartifact-plugin/0e3f0dfc7631424b7bca922a697fd7da071e097f Log: [FIXED JENKINS-15726] Attempting to recover gracefully when upstream file exists but cannot be statted . This message is automatically generated by JIRA. 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-15726) PosixException thrown while changing file mode
Jesse Glick created JENKINS-15726 PosixException thrown while changing file mode Issue Type: Bug Assignee: Jesse Glick Components: copyartifact Created: 05/Nov/12 9:02 PM Description: A user previously encountering JENKINS-14962 now reported an exception: hudson.os.PosixException: /…JENKINS_HOME…/jobs/…/builds/…/archive/…path… ENOENT at hudson.os.PosixAPI$1.error(PosixAPI.java:43) at org.jruby.ext.posix.LinuxPOSIX.stat(LinuxPOSIX.java:89) at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.FilePath$24.invoke(FilePath.java:1369) at hudson.FilePath$24.invoke(FilePath.java:1367) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.mode(FilePath.java:1367) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:79) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyAll(FingerprintingCopyMethod.java:64) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:243) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:215) Not clear what the cause is, since this call to FilePath.mode follows the actual copying of the file, which presumably succeeded. Nonetheless, can at least catch this exception and just log it, since changing file mode is not critical. Project: Jenkins Labels: exception Priority: Minor 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-15702) InstantiationError: hudson.scm.AbstractCvs
Michael Clarke commented on JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs Can you attach your job's config.xml and confirm which version of the CVS plugin you have installed? This message is automatically generated by JIRA. 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-15725) Auto Installation of Ant 1.7.1 fails
Nathan Sharp created JENKINS-15725 Auto Installation of Ant 1.7.1 fails Issue Type: Bug Assignee: Unassigned Components: ant Created: 05/Nov/12 7:01 PM Description: Had a working Jenkins cluster. After upgrading to 1.466.2, many of our builds started failing due to something with the automated ant installation. The console log for the build reports: Unpacking http://archive.apache.org/dist/ant/binaries/apache-ant-1.7.1-bin.zip to C:\hudson\tools\Ant\ant1.7.1 on nightly-win3 FATAL: remote file operation failed: C:\hudson\tools\Ant\ant1.7.1\apache-ant-1.7.1 at hudson.remoting.Channel@74a62a5d:nightly-win3 hudson.util.IOException2: remote file operation failed: C:\hudson\tools\Ant\ant1.7.1\apache-ant-1.7.1 at hudson.remoting.Channel@74a62a5d:nightly-win3 at hudson.FilePath.act(FilePath.java:835) at hudson.FilePath.act(FilePath.java:821) at hudson.FilePath.moveAllChildrenTo(FilePath.java:1543) at hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:76) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:198) at hudson.tasks.Ant$AntInstallation.forNode(Ant.java:371) at hudson.tasks.Ant.perform(Ant.java:151) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.io.IOException: Failed to rename C:\hudson\tools\Ant\ant1.7.1\apache-ant-1.7.1\docs to C:\hudson\tools\Ant\ant1.7.1\docs at hudson.FilePath$32.invoke(FilePath.java:1550) at hudson.FilePath$32.invoke(FilePath.java:1543) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2193) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Note that manually moving that directory works fine. Maybe Jenkins is not properly cleaning up file handles when unpacking the .zip file? This same ant configuration works fine on a Linux slave (but Linux has much less strict file locking). I have worked around the problem for now by making an ant1.7.1 and an ant1.7.1win version in the configuration, where the win version is not attempting to auto-install. Thanks! We love Jenkins Environment: Jenkins is on Ubuntu 12.04 x64 running in glassfish 3.1.1 Failing slaves are Windows XP x32 Project: Jenkins Priority: Critical Reporter: Nathan Sharp This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact yo
[JIRA] (JENKINS-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Jesse Glick resolved JENKINS-15335 as Fixed Jenkins briefly displays build queue and then it disappears until the page is reloaded Right, the reported problem sounds unrelated and should be filed separately. Change By: Jesse Glick (05/Nov/12 6:12 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15513) Invalid .ipa file
Christopher Orr commented on JENKINS-15513 Invalid .ipa file I've been adding support to auto-detect .app vs .ipa files, so perhaps I can submit a patch soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Andreas Zschorn updated JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Change By: Andreas Zschorn (05/Nov/12 5:47 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15699) Improve behaviour of plugin when analyzed code contains compile errors
Mads Nielsen resolved JENKINS-15699 as Fixed Improve behaviour of plugin when analyzed code contains compile errors Implemented in 1.1.1 Change By: Mads Nielsen (05/Nov/12 5:33 PM) Status: Open Resolved Fix Version/s: current 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-14781) Maven Release Plugin performs build without goals
jsirex edited a comment on JENKINS-14781 Maven Release Plugin performs build without goals Looks like this issue is releated to SCM Password. When I perform release build, check "Provide SCM User and Password" and enter an password with " symbol plugin fails. Also, it will be good point to use Jenkins' stored SCM Login/Password, because if I just press release without specifying SCM credentials it fails with "Authentication Failure". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15724) Add option to skip build if change set is empty
Peter Walter edited a comment on JENKINS-15724 Add option to skip build if change set is empty Added a patch to implement the option. This message is automatically generated by JIRA. 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-15724) Add option to skip build if change set is empty
Peter Walter updated JENKINS-15724 Add option to skip build if change set is empty Added a patch to implement teh option. Change By: Peter Walter (05/Nov/12 4:21 PM) Attachment: JENKINS-15724.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-15724) Add option to skip build if change set is empty
Peter Walter created JENKINS-15724 Add option to skip build if change set is empty Issue Type: Improvement Assignee: Jørgen Tjernø Components: pathignore Created: 05/Nov/12 4:18 PM Description: There should be an option to skip the build when the change set is empty. I expected this, as "only build when the changes are (not) matching _expression_ X" should imply "empty change set never matches X" Project: Jenkins Priority: Major Reporter: Peter Walter This message is automatically generated by JIRA. 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-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Greg Allen commented on JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 Think I have found the solution: use the node's build history to find the first failed build. Likely you will find some other error that caused some class to fail initialization. In my case this was: 15:17:40.582 Caused by: java.lang.OutOfMemoryError: PermGen space 15:17:40.582 at hudson.security.PermissionScope.(PermissionScope.java:70) 15:17:40.582 at hudson.security.PermissionScope.(PermissionScope.java:95) 15:17:40.582 at hudson.security.Permission.(Permission.java:178) 15:17:40.582 at hudson.security.Permission.(Permission.java:291) 15:17:40.582 at hudson.scm.SCM.(SCM.java:595) 15:17:40.582 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:776) 15:17:40.582 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:763) 15:17:40.582 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308) 15:17:40.582 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 15:17:40.598 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 15:17:40.598 at hudson.remoting.Request$2.run(Request.java:287) 15:17:40.598 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 15:17:40.598 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 15:17:40.598 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 15:17:40.598 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 15:17:40.598 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 15:17:40.598 at hudson.remoting.Engine$1$1.run(Engine.java:60) 15:17:40.598 at java.lang.Thread.run(Thread.java:619) This very likely explain all your symptoms. Cryptically, because the class fails to initialize, it does not its serialVersionUID does not get initialized, and later the standard Serialization logic will equate this with a serial UID of 1, even though that's not really the case. Hence the unitialised class error turns into an unhelpful incompatible class error. Restarting the slave will of course "fix" the memory issue temporarily. This message is automatically generated by JIRA. 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-15723) When displaying Gravatar, don't draw text on top of it
davidmc24 updated JENKINS-15723 When displaying Gravatar, don't draw text on top of it Change By: davidmc24 (05/Nov/12 3:47 PM) Component/s: jenkinswalldisplay Component/s: walldisplay This message is automatically generated by JIRA. 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-15723) When displaying Gravatar, don't draw text on top of it
davidmc24 created JENKINS-15723 When displaying Gravatar, don't draw text on top of it Issue Type: Improvement Assignee: Christian Pelster Components: walldisplay Created: 05/Nov/12 3:46 PM Description: When using wall display 0.6.15 with the Gravatar feature enabled, some project names may be drawn on top of the Gravatar. I'd prefer that in this case, the names be drawn smaller and displayed to the right of the Gravatar. Project: Jenkins Priority: Minor Reporter: davidmc24 This message is automatically generated by JIRA. 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-15722) Do not echo HTTPS password when cloning
Jesse Glick created JENKINS-15722 Do not echo HTTPS password when cloning Issue Type: Bug Assignee: Jesse Glick Components: mercurial Created: 05/Nov/12 3:41 PM Description: The Mercurial plugin prints the hg clone command it is running. This should mask out any password in the clone URL (when using HTTPS). Also kilnhg.com apparently puts an authentication token into the username field of a URL (the password is ignored but most not be missing lest Hg prompt for it). Ideally this would not be echoed either, though .hg/hgrc will show it to anyone with WORKSPACE permission. Better might be to delete .hg/hgrc#paths.default after cloning and then pass the full URL including authentication fields during subsequent network operations such as pull. Project: Jenkins 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-15638) Xvfb 'display name offset' defaults to 0, not 1 as described, if unset
zregvart resolved JENKINS-15638 as Fixed Xvfb 'display name offset' defaults to 0, not 1 as described, if unset The display name offset property was missing getter, which was reflected in the empty value in configuration screen. Please upgrade to version 1.0.6, and make sure that display name offset is set to something greater than 0. Change By: zregvart (05/Nov/12 3:37 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15721) Cannot add browsers due to template include exception
c089 commented on JENKINS-15721 Cannot add browsers due to template include exception Looking at the git log it seems this was fixed about two months ago, but there is no new release available. This message is automatically generated by JIRA. 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-15638) Xvfb 'display name offset' defaults to 0, not 1 as described, if unset
SCM/JIRA link daemon commented on JENKINS-15638 Xvfb 'display name offset' defaults to 0, not 1 as described, if unset Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java http://jenkins-ci.org/commit/xvfb-plugin/5ddf36dd787e981b6f143973f621d88e0616fa8b Log: JENKINS-15638 Xvfb 'display name offset' defaults to 0, not 1 as described, if unset added missing getter for display name offset This message is automatically generated by JIRA. 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-15721) Cannot add browsers due to template include exception
c089 created JENKINS-15721 Cannot add browsers due to template include exception Issue Type: Bug Assignee: Richard Lavoie Components: selenium Created: 05/Nov/12 3:00 PM Description: When trying to add a browser in the grid config I get: Caused by: org.apache.commons.jelly.JellyTagException: file:/var/lib/jenkins/plugins/selenium/WEB-INF/classes/hudson/plugins/selenium/configuration/browser/webdriver/ChromeBrowser/config.jelly:2:104: No page found '../../AbstractSeleniumBrowser/config.jelly' for class hudson.plugins.selenium.configuration.global.SeleniumGlobalConfiguration Problem seems to be that is uses SeleniumGlobalConfiguration as the working directory, from which this relative path is indeed wrong. Project: Jenkins Priority: Major Reporter: c089 This message is automatically generated by JIRA. 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-15718) Failed to record SCM polling (again) while polling for Clearcase SCM changes
MeTAlMollY commented on JENKINS-15718 Failed to record SCM polling (again) while polling for Clearcase SCM changes Facing the same issue here. From the polling page, I get the following stack-trace. Using Jenkins 1.489 and ClearCase plugin 1.3.11 UCM ClearCase Polling Log Started on Nov 5, 2012 3:15:49 PM [projectA] $ cleartool desc -fmt %[found_bls]Xp\n stream:ProjectA@\projects ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@6946d2[projectA] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(Unknown Source) at hudson.Launcher.inherit(Launcher.java:1068) at hudson.Launcher.access$100(Launcher.java:80) at hudson.Launcher$LocalLauncher.launch(Launcher.java:756) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) This message is automatically generated by JIRA. 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-15156) Builds Disappear from Build History after Completion
Tomas Hellberg commented on JENKINS-15156 Builds Disappear from Build History after Completion My job keeps losing builds from the history all the time. An hour ago there where ten builds in the history, and now only the two most recent builds (out of a total of 175 builds) are shown. All the build data is still available on disk, and the history will show correctly again for a while following a restart of the master. This message is automatically generated by JIRA. 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-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Greg Allen commented on JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 Having the same issue here, but do not have envinject plugin installed at all. Have found that restarting the affected slave temporarily prevents the error. Suspect that your "fix" actually works similarly due to the restart when removing the plugin. My only suspect cause is a minor difference in the JVM versions between master (1.6.0_26) and slave (1.6.0_21) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
Deepak Arora edited a comment on JENKINS-12660 Fail to start the windows service when trying to launch slave node Adding "computername\" before the username worked for me. This message is automatically generated by JIRA. 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-12660) Fail to start the windows service when trying to launch slave node
Deepak Arora commented on JENKINS-12660 Fail to start the windows service when trying to launch slave node Adding "computername\" also worked for me. This message is automatically generated by JIRA. 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-15503) Test results lost on all past builds
Sven Amann resolved JENKINS-15503 as Fixed Test results lost on all past builds The issue has vanished for me as of version 1.487 (stable till 1.489), I consider this as resolved. Change By: Sven Amann (05/Nov/12 1:34 PM) Status: Open Resolved Fix Version/s: current 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-15720) Deploy Artifacts to Maven Repository only resolves Repository ID against POM, not settings.xml
Sven Amann created JENKINS-15720 Deploy Artifacts to Maven Repository only resolves Repository ID against POM, not settings.xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: deploy, maven Created: 05/Nov/12 1:29 PM Description: The "Deploy artifacts to maven repository" action allows for specification of the repository id to name the deploy target. If a respective repository is specified in the projects pom, the id is successfully resolved to the corresponding URL an deploy succeeds. If, however, the repository is specified only in the (global or user) settings.xml file, it is resolved. I see that there is an acceptable workaround and repository URL tend not to change to often, but it would still be nice not to have to retype it for every job. And if you ever have to migrate to a new server, as I just did, it would save some annoyance with correcting the URL in each and every job! Environment: Platform independent Project: Jenkins Priority: Minor Reporter: Sven Amann This message is automatically generated by JIRA. 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-15714) HTTP 500 Internal Exception accessing Maven Repository URL for specific builds
Victor Bronstein commented on JENKINS-15714 HTTP 500 Internal Exception accessing Maven Repository URL for specific builds Initiated pull request for the fix: https://github.com/magnayn/Jenkins-Repository/pull/11 This message is automatically generated by JIRA. 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-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Ognjen Bubalo commented on JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Hi Shane, Unfortunately not. I had a little time and I tried to figure out what is the problem with the charts. I will try to take a look on this today. 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-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.
Shane McEneaney commented on JENKINS-15366 Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods. Hi Ogi, Have you had time to look into this? Thanks, Shane This message is automatically generated by JIRA. 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-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Rune Flobakk commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis I am guessing this is related to classes which are generated, e.g. from WSDLs. A common use case is to generate Java source files which end up in target/generated-sources/**. This folder then becomes part of the source folder of the project, and compiled as usual into target/classes and packaged as usual. But these classes should not be part of the coverage report. In my case, I have a Maven module which only purpose is to generate such classes and package them into a jar. The module does not even have a src-folder because everything is generated from WSDLs/XSDs. The jacoco-maven-plugin correctly does not produce any jacoco.exec file for this module, but it seems like the Jenkins plugin sees the output classes, and no jacoco.exec, and interprets that as zero coverage. This message is automatically generated by JIRA. 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-15718) Failed to record SCM polling (again) while polling for Clearcase SCM changes
Dirk Kuypers commented on JENKINS-15718 Failed to record SCM polling (again) while polling for Clearcase SCM changes Same issue here, downgrading to 1.488 lets the problem disappear. we are also using ClearCase, all my plugins are up to date this morning. This message is automatically generated by JIRA. 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-15718) Failed to record SCM polling (again) while polling for Clearcase SCM changes
Dirk Kuypers edited a comment on JENKINS-15718 Failed to record SCM polling (again) while polling for Clearcase SCM changes Same issue here, downgrading to 1.488 lets the problem disappear. We are also using ClearCase, all my plugins are up to date this morning. This message is automatically generated by JIRA. 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-15719) Builds and workspace disappear for jobs created after upgrade to 1.487
Krzysztof Malinowski created JENKINS-15719 Builds and workspace disappear for jobs created after upgrade to 1.487 Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Nov/12 11:34 AM Description: Recreated from comment in JENKINS-15335: Every new job created post 1.487 have their builds and workspace disappearing on the UI. Reverted to release 1.486 and all builds and workspace are visible. I have observed the same issue for a job that was created as well as for the job being renamed after upgrade. Again, reverting to 1.486 caused the issue to go away. Note that all builds (run both before upgrade and after upgrade) are recorded in JENKINS_HOME and showed up after reverting to 1.486. Jobs that were not renamed or created after upgrade were not affected. Environment: Jenkins 1.487 on RHEL5 x86_64 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. 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-15718) Failed to record SCM polling (again) while polling for Clearcase SCM changes
Waldek M created JENKINS-15718 Failed to record SCM polling (again) while polling for Clearcase SCM changes Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Nov/12 11:18 AM Description: I saw similar issues, but with a bit different stack trace. Captured on Jenkins 1.489 and ClearCase plugin 1.3.11, however CC doesn't appear in the stack trace. ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@103f0bc0[XYZ_R5.0_Integration] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(Unknown Source) at hudson.Launcher.inherit(Launcher.java:1068) at hudson.Launcher.access$100(Launcher.java:80) at hudson.Launcher$LocalLauncher.launch(Launcher.java:756) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Project: Jenkins Labels: jenkins Priority: Major Reporter: Waldek M This message is automatically generated by JIRA. 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Krzysztof Malinowski commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded I'm not sure this is the same issue. Original issue was about build queue (pending jobs) while vijay's issue is about builds and workspace in the job itself. I have also observed it with 1.487 and problem disappeared after reverting to 1.486. I believe it should be reported as a new 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-15717) Failed to monitor warning
David Gang created JENKINS-15717 Failed to monitor warning Issue Type: Bug Assignee: Unassigned Components: slave-status Created: 05/Nov/12 10:31 AM Description: Hi, I am running jenkins v.1487 through tomcat7. I get the error WARNING: Failed to monitor user at slave for Free Swap Space java.io.InvalidClassException: hudson.node_monitors.SwapSpaceMonitor$MonitorTask; local class incompatible: stream classdesc serialVersionUID = 1, local class serialVersionUID = 1184166703664094906 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:562) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1583) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) It seems that this is a bug. I am not familiar enough with jenkins to assess if it can cause great problems, or not. BR, David Project: Jenkins Priority: Minor Reporter: David Gang This message is automatically generated by JIRA. 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-15656) Java Web Start Slave Agent Terminating Connection on Mountain Lion
Fredrik Eldh edited a comment on JENKINS-15656 Java Web Start Slave Agent Terminating Connection on Mountain Lion Same problem, Jenkins 1.488, OSX 10.6, Java 1.6.0_31. Edit: My problem was caused by an incorrect configuration, Remote FS root, which pointed to a path that did not exist. Solved by fixing the config. The error messages shown on both master and slave are still wrong. This message is automatically generated by JIRA. 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-15221) scm_sync_configuration do not synchronize changes made on disk
Wolfgang Hauser edited a comment on JENKINS-15221 scm_sync_configuration do not synchronize changes made on disk with version 0.0.6.1 this problem is still present. This message is automatically generated by JIRA. 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-14781) Maven Release Plugin performs build without goals
jsirex commented on JENKINS-14781 Maven Release Plugin performs build without goals Looks like this issue is releated to SCM Password. When I perform release build, check "Provide SCM User and Password" and enter an password with ' symbol plugin fails. Also, it will be good point to use Jenkins' stored SCM Login/Password, because if I just press release without specifying SCM credentials it fails with "Authentication Failure". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15221) scm_sync_configuration do not synchronize changes made on disk
Wolfgang Hauser commented on JENKINS-15221 scm_sync_configuration do not synchronize changes made on disk with version 0.0.6.1 this problem is already present. This message is automatically generated by JIRA. 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-15656) Java Web Start Slave Agent Terminating Connection on Mountain Lion
Fredrik Eldh commented on JENKINS-15656 Java Web Start Slave Agent Terminating Connection on Mountain Lion Same problem, Jenkins 1.488, OSX 10.6, Java 1.6.0_31. This message is automatically generated by JIRA. 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-15202) Permanent building / consider removing latest changes
Waldek M commented on JENKINS-15202 Permanent building / consider removing latest changes I've finally found some time to verify the fix. Well - it works 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-6604) Possible race condition in RemoteClassLoader renders slave unusable
Erik Lovlie commented on JENKINS-6604 Possible race condition in RemoteClassLoader renders slave unusable Ah yes, it is the same stack trace as above. Didn't notice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
