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

          Activity

            m_broida m_broida added a comment -

            Similarly: renaming (or deleting) a node causes job history entries for jobs built on that node to say they were built on the "master" node instead.

            m_broida m_broida added a comment - Similarly: renaming (or deleting) a node causes job history entries for jobs built on that node to say they were built on the "master" node instead.
            bsipos Brian Sipos added a comment -

            When I rename a job in current version (1.496) the job history disappears immediately, but if I restart the Jenkins service the history reappears under the new job name. Internally, the history files are being moved properly but jenkins doesn't re-load the data into the new project.

            bsipos Brian Sipos added a comment - When I rename a job in current version (1.496) the job history disappears immediately, but if I restart the Jenkins service the history reappears under the new job name. Internally, the history files are being moved properly but jenkins doesn't re-load the data into the new project.
            derek_brown Derek Brown added a comment -

            This one bit us hard today.

            derek_brown Derek Brown added a comment - This one bit us hard today.
            jessarah Jessica Sarah added a comment -

            I have 1.514. After renaming jobs give it sometime to work out the disk files (in my case ~5 min), then click on "Manage Jenkins / Reload Configuration from Disk" and the history was reloaded OK.

            jessarah Jessica Sarah added a comment - I have 1.514. After renaming jobs give it sometime to work out the disk files (in my case ~5 min), then click on "Manage Jenkins / Reload Configuration from Disk" and the history was reloaded OK.

            It looks like a duplicate, but more than one year has passed: JENKINS-18678

            Manually reloading defeats the purpose of automated builds. Also, in my case, I cannot rely on "waiting 5 minutes": it has to be deterministic and it cannot be based on waiting "long enough".

            If a rename requires a reload from disk, then it must do so autonomously without disturbing anything else (current builds, pending builds, etc.).

            The next question that comes to mind is what about dependencies? What if the job I rename is used by another job, say by the Copy the Artifact? Does the rename action take care of updating that other job too?

            deepchip Martin d'Anjou added a comment - It looks like a duplicate, but more than one year has passed: JENKINS-18678 Manually reloading defeats the purpose of automated builds. Also, in my case, I cannot rely on "waiting 5 minutes": it has to be deterministic and it cannot be based on waiting "long enough". If a rename requires a reload from disk, then it must do so autonomously without disturbing anything else (current builds, pending builds, etc.). The next question that comes to mind is what about dependencies? What if the job I rename is used by another job, say by the Copy the Artifact? Does the rename action take care of updating that other job too?
            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.

            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: