Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Major
Component/s: core
Labels:
- 1.509.1-fixed
- issue-exported-to-github

If you set the external builds directory for Jenkins to e.g. /tmp/builds/${ITEM_FULL_NAME} and build some job, then rename it, the existing build records will remain in /tmp/builds/oldname/* and be inaccessible. Similarly, if you delete the job, the build records will be left behind, potentially consuming a great deal of disk space.

is blocking

JENKINS-8446 'builds' directory in a separate location?

Closed

is duplicated by

JENKINS-11716 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

Resolved

is related to

JENKINS-16457 Bogus Jenkins.rawBuildsDir not adequately diagnosed

Resolved

JENKINS-17137 Bogus permalinks created when using external builds directory

Resolved

JENKINS-48188 Broken Symlinks with External Build Record Root Directory and Maven Modules

Open

JENKINS-19764 Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist

Resolved

JENKINS-24825 Missing build history moving a job when BuildDir is set to a custom location

Resolved

JENKINS-44657 Build history not copied after renaming the job's parent folder when using custom build directories

Resolved

(3 is related to)

Assignee:: Jesse Glick
Reporter:: Jesse Glick

Created:: 2013-03-09 00:00
Updated:: 2025-11-25 11:14
Resolved:: 2013-03-09 01:45
Archived:: 2025-11-25 11:14

Details

Description

Attachments

Issue Links

Activity

People

Dates