• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • pipeline
    • None

      Steps to reproduce it:

      1. Create a WF job with some dummy script
      2. Run a build (or two)
      3. Rename the job
      4. Restart Jenkins
      5. You have unreadable data warnings in "Manage Jenkins"

      The root cause is in build.xml files, where the job name is not properly changed in the rename process:

      ...
      <owner class="flow-owner">
          <job>test2</job>
          <id>2015-07-22_13-25-38</id>
      </owner>
      ...
      

      Behavior checked using Jenkins 1.580.2 + Workflow 1.4 and 1.609.1 + Workflow 1.8

          [JENKINS-29571] Unreadable data after renaming a Workflow job

          Antonio Muñiz created issue -
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Link New: This issue depends on JENKINS-27704 [ JENKINS-27704 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 157 (Web Link)" [ 12981 ]
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 164450 ] New: JNJira + In-Review [ 197508 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]
          Andrew Bayer made changes -
          Component/s Original: workflow-plugin [ 18820 ]

            jglick Jesse Glick
            amuniz Antonio Muñiz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: