[JIRA] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500
Christian Apel commented on JENKINS-17734 Claim Report view reports Error Status: 500 I have prepared a pull request (see https://github.com/jenkinsci/claim-plugin/pull/11), which contains a fix for this issue. In addition to that, it's implementing hierarchical support to be used with the CloudBees Folders 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-plugin-gateway] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel commented on JENKINS-17627 NPE while loading Cloudbees folders at Jenkins startup I have downloaded the plugin manually to update Jenkins last Thursday, but after your change there were a few more plugin updates listed (free plugins license, license manager and registration plugin). Thank you for the update and the link to the release notes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-plugin-gateway] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel closed JENKINS-17627 as Fixed NPE while loading Cloudbees folders at Jenkins startup Change By: Christian Apel (29/Apr/13 6:37 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Christian Apel closed JENKINS-16426 as Fixed Backup fails while copying a file from the jobs folder Change By: Christian Apel (29/Apr/13 6:38 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16749) Exception in EmailTrigger
Christian Apel closed JENKINS-16749 as Fixed Exception in EmailTrigger Change By: Christian Apel (29/Apr/13 6:39 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-plugin-gateway] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel commented on JENKINS-17627 NPE while loading Cloudbees folders at Jenkins startup Unfortunately I can't see the 3.6 release in our plugin update center. We currently have configured the following two URLs: http://updates.jenkins-ci.org/update-center.json (main update site) http://jenkins-updates.cloudbees.com/update-center/cloudbees-proprietary/update-center.json (is listed under 'Other Sites') In the above json file, the following URL is listed for the folders plugin: http://jenkins-updates.cloudbees.com/download/plugins/cloudbees-folder/3.5/cloudbees-folder.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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-plugin-gateway] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel updated JENKINS-17627 NPE while loading Cloudbees folders at Jenkins startup Forgot to add the cloudbees-plugin-gateway component. Change By: Christian Apel (24/Apr/13 7:15 AM) Component/s: cloudbees-plugin-gateway This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel created JENKINS-17627 NPE while loading Cloudbees folders at Jenkins startup Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 16/Apr/13 9:23 AM Description: After we have updated Jenkins from version 1.505 to version 1.511, the following exception prevented the Cloudbees folders to load at startup. SEVERE: Failed Loading job modules-spice java.lang.NullPointerException at com.cloudbees.hudson.plugins.folder.Folder.getItem(Folder.java:465) at com.cloudbees.hudson.plugins.folder.Folder.getItem(Folder.java:90) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:746) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:99) at com.cloudbees.hudson.plugins.folder.Folder.onLoad(Folder.java:189) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2554) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:888) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) I couldn't find any issues in JIRA, but according to Vincent's comment http://jenkins.361315.n4.nabble.com/java-lang-NullPointerException-when-loading-folders-tp4661608p4661953.html, this should be a regression in Jenkins core. What could we do to update to the latest version? Right now it looks like the issue still exists in version 1.511 and the mentioned Cloudbees folders plugin 3.6 is not yet listed in the update list. Is it possible that this release is not available in the Cloudbees free plugins, but just in Jenkins Enterprise? Environment: Windows Server 2008 R2 64bit, Tomcat 7, Jenkins 1.505, latest versions of Cloudbees free plugins Project: Jenkins Priority: Major Reporter: Christian Apel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Christian Apel commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs I have tested the latest Jenkins release 1.511, but had to downgrade again to version 1.505 due to JENKINS-17627. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Christian Apel commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Thanks for the hint. We are still on version 1.505 because of the issue JENKINS-17264, which has been introduced in version 1.506. But according to the latest comment of yesterday, the current snapshot of the m2release-plugin should solve this issue. I will try to install the latest Jenkins version in the next few days. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Christian Apel commented on JENKINS-16845 NullPointer in getPreviousBuild Is this issue related to JENKINS-15652? We currently have dead executors every day, because of the following exception (see full stack trace in my comment): java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1053) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-failure-analyzer] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Christian Apel commented on JENKINS-15948 Analyzer Icons arent displayed if Jenkins isnt installed at root context. The duplicate 'jenkins' in the URL was introduced in the plugin update from version 1.4.0 to 1.4.1. Our Jenkins location URL is set to 'http://host:8080/jenkins/'. http://host:8080/jenkins/jenkins/plugin/build-failure-analyzer/images/48x48/information.png http://host:8080/jenkins/jenkins/plugin/build-failure-analyzer/images/24x24/newinformation.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Christian Apel commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs We have the same issue with Jenkins 1.505 (running on Windows Server 2008 R2 Standard 64bit, deployed in a Tomcat 6 which is configured as a Windows service). In the last few days, I have found all executors dead every morning when I came into the office. This has started suddenly without any configuration changes or complex software updates, but after we have added approximately 400 further builds. Wouldn't it be an option to make the lazy loading configurable, so that this could be at least temporarily fixed? java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1053) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:877) at hudson.model.Job.getEstimatedDuration(Job.java:888) at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:320) at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:303) at hudson.model.Queue.maintain(Queue.java:1035) at hudson.model.Queue.pop(Queue.java:863) at hudson.model.Executor.grabJob(Executor.java:285) at hudson.model.Executor.run(Executor.java:206) 08.04.2013 08:41:45 hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: item.isStuck() in /jenkins/. Reason: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1053) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:877) at hudson.model.Job.getEstimatedDuration(Job.java:888) at hudson.model.Queue$BuildableItem.isStuck(Queue.java:1654) at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-16749) Exception in EmailTrigger
Christian Apel commented on JENKINS-16749 Exception in EmailTrigger In the affected build jobs, we are using an SCM trigger (scheduled SVN server polling) and the 'Build other projects' function. The exception was thrown in builds which were triggered by one of these two triggers. It was not yet thrown if a build was started 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16749) Exception in EmailTrigger
Christian Apel created JENKINS-16749 Exception in EmailTrigger Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 11/Feb/13 8:47 AM Description: One of our recent builds failed due to the below exception, even though the build had finished without any issues. Checking if email needs to be generated ERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.emailext.plugins.EmailTrigger.getNumFailures(EmailTrigger.java:70) at hudson.plugins.emailext.plugins.trigger.RegressionTrigger.trigger(RegressionTrigger.java:23) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:260) 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.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:970) at hudson.model.Run.execute(Run.java:1587) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Finished: FAILURE Project: Jenkins Priority: Major Reporter: Christian Apel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16749) Exception in EmailTrigger
Christian Apel commented on JENKINS-16749 Exception in EmailTrigger We are using the latest release version 2.25. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Christian Apel commented on JENKINS-16426 Backup fails while copying a file from the jobs folder Thanks for your detailed explanation. These files are more related to the job configurations but not to the global Jenkins configuration. I think that it's a good idea to move them to the userContent folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Christian Apel commented on JENKINS-16426 Backup fails while copying a file from the jobs folder We had stored some Maven settings.xml files within the jobs directory (just to use the same configuration in multiple build jobs). There are no files which were generated by any of our Jenkins plugins. As I have seen, the above commit is now ignoring the files, which should of course also be saved in the backups. We have now temporarily copied the files to the build job directories, but would appreciate to have the ability to move them back to the jobs folder. Is there any reason why files shouldn't be stored in this directory? Or should we use another subdirectory of the Jenkins root folder, which is automatically saved in the backups? This message is automatically generated by JIRA. 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-13019) Add option 'Preselect specify SCM login/password' and set default user name to Jenkins user
Christian Apel resolved JENKINS-13019 as Fixed Add option Preselect specify SCM login/password and set default user name to Jenkins user Was fixed in m2release-0.9.0 (commit https://github.com/jenkinsci/m2release-plugin/commit/670327c36d8b00c853d5e0f225529fff11e2868d) Change By: Christian Apel (24/Jan/13 12:42 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-13019) Add option 'Preselect specify SCM login/password' and set default user name to Jenkins user
Christian Apel closed JENKINS-13019 as Fixed Add option Preselect specify SCM login/password and set default user name to Jenkins user Was implemented in m2release-0.9.0. Change By: Christian Apel (24/Jan/13 12:44 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-16426) Backup fails while copying a file from the jobs folder
Christian Apel created JENKINS-16426 Backup fails while copying a file from the jobs folder Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 21/Jan/13 8:51 AM Description: It looks like the backup plugin tries to copy a directory instead of a file and stops the backup at this point. Also the configured compression to zip files wasn't working, probably due to the exception. Jan 21, 2013 5:00:34 AM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 31 jobs to back up. Jan 21, 2013 5:00:34 AM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 347 jobs to back up. Jan 21, 2013 5:00:36 AM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 36 jobs to back up. Jan 21, 2013 5:00:38 AM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'D:\backup\jenkins'. java.io.IOException: Source 'd:\jenkins\jobs\settings-XYZ.xml' exists but is not a directory at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:869) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobConfigFor(HudsonBackup.java:240) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:201) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:190) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:169) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:136) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.execute(ThinBackupPeriodicWork.java:68) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Thread.java:722) I haven't recognized this issue immediately, because a full backup and 6 incremental backups were partially stored in the backup folder. It would be helpful to show an error on the thinBackup Jenkins page, if a backup failed due to any issue. Environment: Windows Server 2008 R2 64bit, Tomcat 7 Project: Jenkins Priority: Major Reporter: Christian Apel This message is automatically generated by JIRA. 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-16091) Aborted builds are repeated within subsequent builds
Christian Apel created JENKINS-16091 Aborted builds are repeated within subsequent builds Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: core, release Created: 11/Dec/12 8:57 AM Description: If a user is starting a build (e.g. a maven release build with command line parameters including SVN credentials) and this build is aborted by the server, we have identified an issue with the subsequent build. Builds which are aborted by the server are repeated within the following build (even if a different user has started a different build type). We had the issue that another user wanted to start a SNAPSHOT build by clicking on the "Build Now" link, but a "Maven release build" was started instead. This release build was triggered by the current user, but contained the command line parameters of the previously aborted release build. If a build is aborted by the server, it must be ensured that subsequent builds are not started with optional or user defined parameters. Project: Jenkins Priority: Critical Reporter: Christian Apel This message is automatically generated by JIRA. 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-15926) Build Failure Analyzer with Timestamper output ugly.
Christian Apel commented on JENKINS-15926 Build Failure Analyzer with Timestamper output ugly. We are not using the timestamper plugin, but also get such output in our build logs. It looks like these lines are randomly added, because they are not just added to failure lines. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
