-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: pipeline-model-definition-plugin
-
Labels:None
-
Similar Issues:
After upgrading to BlueOcean 1.3 and Jenkins 2.73.2, I encountered some warning about old data structure (see attached screenshot).
Though my job is still able to run, I'm not sure if there are any problems with this, as per the description in this page, the data in my old structure will be loaded first without change the location on disk, but in this case it seems failed to load.
Please advise what should I do now.
- links to
Code changed in jenkins
User: Andrew Bayer
Path:
pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/actions/ExecutionModelAction.java
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/342ca4ccb43d3d07fc7ccf6612412b21f1006518
Log:
[FIXED JENKINS-47421] Make sure we init stagesList in readResolve
This is a very minor issue in practice - the ExecutionModelAction
isn't really used by anything but our own check for multiple executed
pipeline blocks, which itself can't ever be the case on builds that
started before Declarative 1.2 in the first place. Buuuuut it does
result in some weird unreadable data messages in Jenkins, so let's
play things very safe.
Bulk closing resolved issues.
I've got a PR up that'll address this going forward, but in practice, you can just re-save the builds in question as suggested on that page and you'll be fine. The bit that's not converting properly is only relevant at runtime, and really only relevant with builds started with Declarative 1.2 and later...none of which would have the readResolve issue since they've already got the data in the right place. So yeah, you should be fine in practice and the next release will make sure to get rid of these messages.