-
Bug
-
Resolution: Fixed
-
Critical
-
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
- depends on
-
JENKINS-27704 Clean up build record storage
-
- In Progress
-
- links to
Code changed in jenkins
User: Jesse Glick
Path:
aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java
http://jenkins-ci.org/commit/workflow-plugin/9d087ca7fcb3e6f186d3f44f289bae8861dedad7
Log:
JENKINS-29571reproduced in test and confirmed to depend on part of JENKINS-27704.