[
https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158847#comment-158847
]
Steve Roth commented on JENKINS-11716:
--------------------------------------
This is still an issue in Jenkins 1.450
> Renaming a job does not rename the build record root dir, for a Jenkins
> instance configured with this feature
> -------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-11716
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11716
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Reporter: Steve Roth
>
> We have a Jenkins instance (1.438) using the 'Build Record Root Directory'
> feature, so we can specify an alternate directory for storing build artifacts
> outside of the JENKINS HOME directory.
> This generally works fine. However, I noticed that when I rename a job, I
> lose the previous build records.
> I see a new build record directory is created, beneath the specified 'Build
> Record Root Directory'. However, the old build directory also exists,
> containing the previous records. They are not moved over to the new
> directory.
> In other words, when the 'Build Record Root Directory' feature is enabled,
> renaming a project causes the project's build records to be lost.
> Current workaround is to move the build record files over and use sed to
> replace the project name in them, then restart Jenkins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
