Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44657

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 2.46.3; Mac OS X
    • Similar Issues:

      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

            Activity

              People

              • Assignee:
                rsandell rsandell
                Reporter:
                recampbell recampbell
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: