Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Jenkins 2.46.3; Mac OS X
Description
If you have configured Jenkins to use custom build directories and then rename a folder, the builds from any jobs in those folders are not correctly copied to the target folder.
Steps to reproduce
1. Configure Jenkins to use a custom build directory
2. Create a folder
3. In that folder, create a freestyle job
3.1. Add a shell step with the text "artifact.txt"
3.2. Add a post-build action to archive the artifacts
4. Run the freestyle job
5. See that the builds are showing up in the custom build directory
6. Rename the folder
7. Navigate to the job in the new folder
8. Click on the build run earlier
Actual Result
The build logs and artifacts are missing from build #1 as seen in the screen shot after rename. Furthermore, if you restart Jenkins, the build history is completely lost.
Expected Result
The build logs and artifacts should not be lost. Restarting Jenkins should not result in the loss of build history.
Attachments
Issue Links
- is duplicated by
-
JENKINS-33941 When using a custom build directory, the renaming a job folder does not initially carry over previous builds
-
- Closed
-
- is related to
-
JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds
-
- Resolved
-
- relates to
-
JENKINS-26838 Utility API to check if a file is physically inside a given directory
-
- Open
-
- links to
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/Util.java
http://jenkins-ci.org/commit/jenkins/6a4d800091926c5484483f79e8936ac9d21d67a1
Log:
JENKINS-44657Noting when #2932 was merged.