[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Title: Message Title Forest Handford commented on JENKINS-26519 Re: Build records not migrated due to “failed to rename” on Windows FYI: I ran into this same issue on CentOS 6.5. Old directories had symlinks like: lrwxrwxrwx. 1 jenkins jenkins 19 Apr 22 09:06 401 -> 2015-04-22_09-06-23 New directories looked like: drwxr-xr-x. 2 jenkins jenkins 4096 Mar 1 01:28 317 The UI showed the old builds as having run before I was born! In order to re-run the migration I did the following: sudo find /var/lib/jenkins/ -name legacyIds -delete sudo service jenkins restart Once this was done things looked correct. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Integrated in jenkins_main_trunk #3961 JENKINS-26519 Attempting to improve diagnostics in case rename fails. (Revision 4a75e058bafd3cd98832a2a129c9f23c71d26f55) JENKINS-26519 More diagnostics in case a numeric rename target already exists. (Revision 22dc8add0e106d100a73c16cb628f1c5d1f94538) [FIXED JENKINS-26519] Build record migration failed on Windows using Java 6. (Revision 7f82ab94a4f6247abaf9f65998360be5c3136bf8) Result = SUCCESS jesse glick : 4a75e058bafd3cd98832a2a129c9f23c71d26f55 Files : core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java jesse glick : 22dc8add0e106d100a73c16cb628f1c5d1f94538 Files : core/src/main/java/jenkins/model/RunIdMigrator.java jesse glick : 7f82ab94a4f6247abaf9f65998360be5c3136bf8 Files : core/src/test/java/jenkins/model/RunIdMigratorTest.java core/src/main/java/jenkins/model/RunIdMigrator.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/7f82ab94a4f6247abaf9f65998360be5c3136bf8 Log: [FIXED JENKINS-26519] Build record migration failed on Windows using Java 6. In this environment, Util.createSymlink and .isSymlink are implemented, but resolveSymlink is not. (cherry picked from commit 388c4b5e6ba52037cae117c5c69f9f4156d41401) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/1debf06fe6d6...7f82ab94a4f6 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/4a75e058bafd3cd98832a2a129c9f23c71d26f55 Log: JENKINS-26519 Attempting to improve diagnostics in case rename fails. (cherry picked from commit 0633beef0868c59a7e853731aee5f5c0745fa3fc) This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/RunIdMigrator.java http://jenkins-ci.org/commit/jenkins/22dc8add0e106d100a73c16cb628f1c5d1f94538 Log: JENKINS-26519 More diagnostics in case a numeric rename target already exists. (cherry picked from commit 75c8c31f2fdc98081a0446dd3ee03da7243304a1) This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Yeah! That's it. No more 45 year old builds Thank you so much for your efforts. I very much appreciate it! --Heiko This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Integrated in jenkins_main_trunk #3958 [FIXED JENKINS-26519] Build record migration failed on Windows using Java 6. (Revision 388c4b5e6ba52037cae117c5c69f9f4156d41401) Result = SUCCESS jesse glick : 388c4b5e6ba52037cae117c5c69f9f4156d41401 Files : changelog.html core/src/test/java/jenkins/model/RunIdMigratorTest.java core/src/main/java/jenkins/model/RunIdMigrator.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 -- 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows tdtappe I think your problem is now fixed in this build, toward 1.600. If you confirm I will try to backport it to the 1.599 release candidate branch so it gets out earlier. Steve Haworth My latest fix might help in your case, but since you say you are running Java 8, you should not have been hitting it to begin with. Your symptoms are similar; the root cause may or may not be related. I would suggest trying once again with my newest build, assuming you still have the original build directories to reproduce against. First be sure to enable fine logging on this component. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon resolved JENKINS-26519 as Fixed Build records not migrated due to “failed to rename” on Windows Change By: SCM/JIRA link daemon (29/Jan/15 8:41 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
SCM/JIRA link daemon commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/model/RunIdMigrator.java core/src/test/java/jenkins/model/RunIdMigratorTest.java http://jenkins-ci.org/commit/jenkins/388c4b5e6ba52037cae117c5c69f9f4156d41401 Log: [FIXED JENKINS-26519] Build record migration failed on Windows using Java 6. In this environment, Util.createSymlink and .isSymlink are implemented, but resolveSymlink is not. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Confusingly, for Windows on Java 6, 1, 2, etc. were created as true symlinks; the text files with build numbers were only used for permalinks like lastStableBuild, meaning my attempted fix in 056b446 was pointless and can probably just be reverted. (One of the unusual cases where “reopening” a bug is really 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 -- 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Ah, I was wrong, 1.596- on Windows Java 6 did attempt to create symlinks, using JNA, and this does produce the described error. So that is something I can and will fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Also I checked in jrunscript under these circumstances that the code called by Util.resolveSymlink would work, as would the call to Util.deleteFile. In the case of tdtappe, running Java 6, resolveSymlink would be expected to fail, explaining the skipping deletion of directory … message, followed by the failure of the migrator. (Which as I mentioned before would not be expected to matter for most people because symlinks should not have been created to begin with; need to confirm this.) This I could fix by just trying deleteFile anyway—if it is really a symlink to a directory, that will work, but if it is really a directory, it should fail because the directory is not empty. It makes me a little nervous because isDirectory would also be true for a real directory created by 1.597+ (or a partly successful earlier migration), and relying on File.delete to fail in this case seems dangerous. In the case of Steve Haworth, running Java 8, I am puzzled. I see no FINE-level messages here so I assume you did not turn on the custom logger, which might have some crucial 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 -- 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Also I checked in jrunscript under these circumstances that the code called by Util.resolveSymlink would work, as would the call to Util.deleteFile. In the case of tdtappe, running Java 6, resolveSymlink would be expected to fail, explaining the skipping deletion of directory … message. This I could fix by just trying deleteFile anyway—if it is really a symlink to a directory, that will work, but if it is really a directory, it should fail because the directory is not empty. It makes me a little nervous because isDirectory would also be true for a real directory created by 1.597+ (or a partly successful earlier migration), and relying on File.delete to fail in this case seems dangerous. In the case of Steve Haworth, running Java 8, I am puzzled. I see no FINE-level messages here so I assume you did not turn on the custom logger, which might have some crucial 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 -- 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Could not reproduce by starting Jenkins 1.596 on Windows 2012 as Administrator under JDK 7u21, creating a project, running a few builds, then stopping and starting a trunk build: builds got correctly migrated. So perhaps only arises under specific circumstances. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows
Jesse Glick updated JENKINS-26519 Build records not migrated due to “failed to rename” on Windows Yes one workaround would be delete all numeric SYMLINKD, though I am not sure if there is an easy batch command to do that. Still intend to try to reproduce this and offer a proper fix. Change By: Jesse Glick (29/Jan/15 4:51 PM) Summary: Build records not migrated due to “failed to rename” on Windows esp. on Java 6 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Build #3957 Log extract... 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-10_17-23-06 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\273 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\GEMTEST_Page_84\builds\2014-12-23_14-42-31 java.io.IOException: C:\Jenkins\jobs\GEMTEST_Page_84\builds\1420 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-26_13-03-35 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\288 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) Jenkins is running on a Virtual Machine with - Windows Server 2008 R2 Standard with Service Pack 1 Java version is - Java Standard Edition Version 8 Update 31 NOTE: Tried experiment... if I manually delete the shortcut directories in a job directory then migration is okay This message is automatically generated by JIRA. 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
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Build #3957 Log extract... 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-10_17-23-06 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\273 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\GEMTEST_Page_84\builds\2014-12-23_14-42-31 java.io.IOException: C:\Jenkins\jobs\GEMTEST_Page_84\builds\1420 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) 29-Jan-2015 10:40:35 jenkins.model.RunIdMigrator doMigrate WARNING: failed to process C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\2014-11-26_13-03-35 java.io.IOException: C:\Jenkins\jobs\STX_USM_XFF-CAMARO_Package\builds\288 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) Jenkins is running on Running on a Virtual Machine with - Windows Server 2008 R2 Standard with Service Pack 1 Java version is - Java Standard Edition Version 8 Update 31 NOTE: Tried experiment if I manually delete the shortcut directories in a job directory then migration is okay This message is automatically generated by JIRA. 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 subscri
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Another excerpt with newest build: Jan 29, 2015 8:50:35 AM WARNUNG jenkins.model.RunIdMigrator doMigrate failed to process d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\2014-10-16_10-32-01 java.io.IOException: d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\68 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5995 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5996 Jan 29, 2015 8:50:35 AM WARNUNG jenkins.model.RunIdMigrator doMigrate failed to process d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\2014-11-05_16-13-26 java.io.IOException: d:\NightlyBuilds\Jenkins\jobs\KomalogWin - tag\builds\69 already exists at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:274) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:281) at jenkins.model.Jenkins$17.run(Jenkins.java:2673) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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) Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5997 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 5998 Jan 29, 2015 8:50:35 AM INFO jenkins.model.RunIdMigrator migrate Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.01-dev\builds Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 124 Jan 29, 2015 8:50:35 AM FEIN jenkins.model.RunIdMigrator doMigrate skipping deletion of directory 128 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Daniel Beck commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Jesse: Could the unexpected XML come from running the unmigration script? This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 tdtappe Well I will check once I get a post-XP test system up. My reading of the code in older versions of Jenkins is that it would never create such a symlink when running on Java 6, but I may have missed something. Steve Haworth Odd. The build is recorded as having been created by Jenkins 1.590, so before the switch, yet it has and no number, like the new format, but no , like the old format. The migrator intentionally tries the folder rename before the build.xml rewrite, so it should not have been the result of an error midway through migration. So I have no explanation for how you got there and hope this is rare enough. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Attached 2014-11-26_03-40-28 build.xml This is one of the files indicated in log "jenkins.err.log_on-startup.txt" as having no number. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Steve Haworth updated JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Change By: Steve Haworth (28/Jan/15 5:53 PM) Attachment: 2014-11-26_03-40-28 build.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Integrated in jenkins_main_trunk #3957 JENKINS-26519 More diagnostics in case a numeric rename target already exists. (Revision 75c8c31f2fdc98081a0446dd3ee03da7243304a1) Result = UNSTABLE jesse glick : 75c8c31f2fdc98081a0446dd3ee03da7243304a1 Files : core/src/main/java/jenkins/model/RunIdMigrator.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 -- 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 BTW I could most probably switch to Java 7 or even 8 on that machine if it might solve all my problems. But then we (you) wouldn't have a problematic real time scenario any longer to test with Java 6!? This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 I am almost 100% sure that there never has been another Java version than 6 (since 2010) on that machine. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 OK, the 116+ builds are either new, or got correctly migrated, but then we also got skipping deletion of directory 4 where this one was an old build with a SYMLINKD that did not get migrated. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 The question is how you even got these build number symlinks to begin with—as far as I know they are not created when you run Jenkins on Windows using Java 6! (Even if the Windows system supports symlinks generally; IIRC XP does not, and newer systems may or may not.) The only way I can think to make them appear is to run 1.596- using Java 7, at least for a while, then run 1.597+ using Java 6. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
tdtappe commented on JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Actually not: Datentr„ger in Laufwerk D: ist DATEN Volumeseriennummer: 1225-FEC9 Verzeichnis von D:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.02.00-patched\builds Mi 28.01.2015 16:12 . Mi 28.01.2015 16:12 .. Di 20.01.2015 02:57 116 Sa 24.01.2015 02:51 121 Di 27.01.2015 02:51 122 Mi 28.01.2015 02:55 123 Fr 29.08.2014 03:25 2014-08-29_03-51-39 Fr 29.08.2014 02:51 4 [2014-08-29_03-51-39] Fr 19.12.2014 02:57 2 lastFailedBuild Mi 28.01.2015 02:55 3 lastStableBuild Mi 28.01.2015 02:55 3 lastSuccessfulBuild Mi 27.08.2014 07:19 2 lastUnstableBuild Fr 19.12.2014 02:57 2 lastUnsuccessfulBuild Mi 28.01.2015 16:12 0 legacyIds 6 Datei(en), 12 Bytes 8 Verzeichnis(se), 769.188.323.328 Bytes frei This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename” on Windows esp. on Java 6
Jesse Glick updated JENKINS-26519 Build records not migrated due to “failed to rename” on Windows esp. on Java 6 Change By: Jesse Glick (28/Jan/15 3:41 PM) Summary: Build records not migrated due to “failed to rename " ” on Windows esp. on Java 6 This message is automatically generated by JIRA. 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/d/optout.
