[
https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158869#comment-158869
]
Steve Roth commented on JENKINS-11716:
--------------------------------------
I was able to reproduce using a vanilla OOTB Jenkins install.
Steps to repro:
1- Install Jenkins
2- Go to Manage / Configure page, click Advanced... button at top of screen,
set Build Record Root Directory to /scratch/jbuildroot/${ITEM_FULLNAME}/builds
or something like that, click Save
3- Create a test job with a shell script section, do a few runs, note the logs
are saved to /scratch/jbuildroot/JOBNAME/builds
4- Rename the test job. Note there is a new dir at
/scratch/jbuildroot/NEWJOBNAME/builds but it has one empty run. The old runs
are still under /scratch/jbuildroot/JOBNAME/builds
5- Restart Jenkins via yourhost:8080/restart
6- Note the test job runs are gone because the Build Records were not moved to
the new dir.
> 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
