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

[jgl...@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename" In the interest of expediency I pushed what I think is a fix to the rc branch for 1.598 (which will I guess come out on Monday as usual), and am validating a merge to master. It would not be a bad idea to grab the jenkins.war from https://jenkins.ci.cloudbees.com/job/core/job/jenkins_rc_branch/317/ once it completes and try running it. In order to force a rerun of migration when using the patched version of Jenkins: Shut down Jenkins. Delete all %JENKINS_HOME%\jobs*\builds\legacyId files. (They are just caches and will be recreated as needed.) Start Jenkins again. Check the log file. You should see the Migrating build records messages again, but should not see the warnings.

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.