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

renaming a job does not preserve history

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Duplicate
    • core
    • None

    Description

      When you rename a job, the history on the job is lost. I don't see any reason why this should happen and should at least be a choice.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-18678 Builds disappear some time after renaming job

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-15979 "forgets" builds, workspace of renamed job

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 5 older comments
            jessarah Jessica Sarah added a comment - - edited

            FYI: The renaming of the jobs, in my case, was propagated to other jobs using it. While reloading from disks it did not disturb running jobs.

            jessarah Jessica Sarah added a comment - - edited FYI: The renaming of the jobs, in my case, was propagated to other jobs using it. While reloading from disks it did not disturb running jobs.
            derek_brown Derek Brown added a comment -

            The rename action does take care of updating jobs that use Copy Artifact and dependencies.

            derek_brown Derek Brown added a comment - The rename action does take care of updating jobs that use Copy Artifact and dependencies.
            sarahwoodall Sarah Woodall added a comment -

            You only need to reload the configuration manually from disk after you have renamed a job, as far as I can see. After you have done that, your history is reinstated. So this bug is frightening, because it looks as though the history has been lost, but it turns out to be harmless.

            sarahwoodall Sarah Woodall added a comment - You only need to reload the configuration manually from disk after you have renamed a job, as far as I can see. After you have done that, your history is reinstated. So this bug is frightening, because it looks as though the history has been lost, but it turns out to be harmless.
            lawtondevinec Craig Lawton-Devine added a comment -

            I renamed a job today and the history was not lost.
            No manual steps were required and the history was there instantly.

            The only issue I've had is that a downstream job that runs on promotion of the renamed job still referred to the old job name.

            lawtondevinec Craig Lawton-Devine added a comment - I renamed a job today and the history was not lost. No manual steps were required and the history was there instantly. The only issue I've had is that a downstream job that runs on promotion of the renamed job still referred to the old job name.
            oleg_nenashev Oleg Nenashev added a comment -

            The issue has been solved in JENKINS-18678

            oleg_nenashev Oleg Nenashev added a comment - The issue has been solved in JENKINS-18678

            People

              Unassigned Unassigned
              bnovc bnovc
              Votes:
              10 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: