-
Bug
-
Resolution: Duplicate
-
Minor
-
None
If someone is using a custom build directory, when trying to move Jobs between folders it will not carry over the build history until the configuration is edited and saved.
So with every job that is moved using either the move/copy/promote or moving it inside of the file system they have to hit Configure then save in order to see previous build info.
- duplicates
-
JENKINS-44657 Build history not copied after renaming the job's parent folder when using custom build directories
-
- Resolved
-
- links to
[JENKINS-33941] When using a custom build directory, the renaming a job folder does not initially carry over previous builds
Assignee | New: Kristin Whetstone [ kwhetstone ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Workflow | Original: JNJira [ 169952 ] | New: JNJira + In-Review [ 185708 ] |
Summary | Original: When using a custom build directory, the moving a job folder does not initially carry over previous builds | New: When using a custom build directory, the renaming a job folder does not initially carry over previous builds |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
I've been looking at this and found some other odd behavior depending on the different combinations of home directories. Investigating and fixing.