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

Wed, 21 Jan 2015 23:23:36 -0800

tdtappe commented on Bug JENKINS-26519

Switched to Jenkins ver. 1.598-SNAPSHOT (rc-01/21/2015 18:23 GMT-jenkins) after having deleted the legacyIds files. But still:

...
...
22.01.2015 08:13:43 jenkins.model.RunIdMigrator migrate
INFO: Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 14.02-dev\builds
22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate
WARNUNG: failed to rename 2014-08-30_00-58-41 to 79
22.01.2015 08:13:43 jenkins.model.RunIdMigrator migrate
INFO: Migrating build records in d:\NightlyBuilds\Jenkins\jobs\KomalogWin - 12.01.02-patched\builds
22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate
WARNUNG: found no build.xml in 2012-12-07_00-13-31
22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate
WARNUNG: failed to rename 2013-03-01_00-22-07 to 271
22.01.2015 08:13:43 jenkins.model.RunIdMigrator doMigrate
WARNUNG: failed to rename 2015-01-20_01-45-40 to 82
22.01.2015 08:13:43 jenkins.model.RunIdMigrator migrate
...
...
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to