[
https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Roth updated JENKINS-11716:
---------------------------------
Summary: When 'Build Record Root Directory' is enabled, renaming a job
does not create a new BRRD dir for the renamed job, and does not rename/copy
artifacts from the original BRRD (was: Renaming a job does not rename the
build record root dir, for a Jenkins instance configured with this feature)
Description:
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.
The 'Build Record Root Directory' (set in configure system, then click
Advanced... button at the top), is set to
/scratch/jbuildroot/${ITEM_FULLNAME}/builds. The Workspace Root dir is set to
${ITEM_ROOTDIR}/workspace.
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.
was:
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.
I noticed that in Jenkins v1.454, renaming a job does not even create the build
record root dir entry. For example, if I have build record root dir set to
/scratch/jbuildroot/${ITEM_FULLNAME}/builds and I rename a job 'foo' to 'bar',
then /scratch/jbuildroot/foo exists, but the rename does not create
/scratch/jbuildroot/bar.
I think in a previous version, this directory was at least created (though it
was empty), but in v1.454, I dont see it created anymore.
Updating the summary to reflect the new information.
> When 'Build Record Root Directory' is enabled, renaming a job does not create
> a new BRRD dir for the renamed job, and does not rename/copy artifacts from
> the original BRRD
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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.
> The 'Build Record Root Directory' (set in configure system, then click
> Advanced... button at the top), is set to
> /scratch/jbuildroot/${ITEM_FULLNAME}/builds. The Workspace Root dir is set
> to ${ITEM_ROOTDIR}/workspace.
> 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
