Renaming a folder within a specified custom directory requires manual clean up

Issue

Renaming a folder within a specified custom directory requires manual clean up

Environment

CloudBees Jenkins Enterprise

CloudBees Jenkins Operations Center

Resolution

Renaming a folder that is located in a custom directory vs. the default Jenkins_home location will
require the directory with the folder’s previous name to be removed manually. Please also note
that it is the user’s responsibility to move the build data from the old location to the new location.

Example
You are using the following custom directory: ~/myBuildHistory to hold the build data of jobs.

A folder named TeamOne is created and contains the jobs, build data, and artifacts associated with this team.
The directory for the TeamOne folder is: ~/myBuildHistory/TeamOne .

The folder is renamed to TeamA. This causes the following directory: ~/myBuildHistory/TeamA to be created which
will contain the jobs, build data, and artificats. However, the initial directory ~/myBuildHistory/TeamOne still exists and contains all of the data generated prior to the folder being renamed. The initial directory, ~/myBuildHistory/TeamOne will need to be deleted manually to free up the disk space it is using.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.