[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename"

[dogf...@java.net (JIRA)]

dogfood commented on JENKINS-26519 Build records not migrated due to “failed to rename" Integrated in jenkins_main_trunk #3940 JENKINS-26519 Confirming that it is safe to rerun migration by just deleting legacyId files. (Revision c997ac0c865ca4866ffda0e9ae93fe818c311cba) [FIXED JENKINS-26519] Accept Windows text file quasi-symlinks for build numbers. (Revision 056b446480d9f24619c2c30ebdf9df6122a9b653) Result = SUCCESS jesse glick : c997ac0c865ca4866ffda0e9ae93fe818c311cba Files : core/src/test/java/jenkins/model/RunIdMigratorTest.java jesse glick : 056b446480d9f24619c2c30ebdf9df6122a9b653 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.