-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins:2.74
Blue Ocean: 1.2.0
-
-
Blue Ocean 1.2, Blue Ocean 1.3
After recent upgrade to 1.2.0 the existing views are broken with the following error. Not sure if it is going to be the same problem for the new runs, yet to try out. Appreciate some inputs?
Error rendering PipelineRunGraph: TypeError: Cannot read property 'name' of undefined
- is related to
-
JENKINS-47480 Blue Ocean: Error rendering PipelineRunGraph
-
- Closed
-
- links to
[JENKINS-46436] Blue Ocean: Error rendering PipelineRunGraph
Description |
Original:
After recent upgrade to 1.2.0 the existing view are broken with the following error. Not sure it is going to be the same problem for the new runs, yet to try out. {code} Error rendering PipelineRunGraph: TypeError: Cannot read property 'name' of undefined {code} |
New:
After recent upgrade to 1.2.0 the existing views are broken with the following error. Not sure if it is going to be the same problem for the new runs, yet to try out. {code:java} Error rendering PipelineRunGraph: TypeError: Cannot read property 'name' of undefined {code} |
Description |
Original:
After recent upgrade to 1.2.0 the existing views are broken with the following error. Not sure if it is going to be the same problem for the new runs, yet to try out. {code:java} Error rendering PipelineRunGraph: TypeError: Cannot read property 'name' of undefined {code} |
New:
After recent upgrade to 1.2.0 the existing views are broken with the following error. Not sure if it is going to be the same problem for the new runs, yet to try out. Appreciate some inputs? {code:java} Error rendering PipelineRunGraph: TypeError: Cannot read property 'name' of undefined {code} |
Issue Type | Original: New Feature [ 2 ] | New: Bug [ 1 ] |
Epic Link | New: JENKINS-35761 [ 171656 ] |
Sprint | New: Blue Ocean 1.2 [ 376 ] |
Attachment | New: Chrome Error.png [ 39454 ] |
Assignee | New: Josh McDonald [ sophistifunk ] |
nrayapati unfortunately not enough information. Are all your plugins up to date? Can you share a Jenkinsfile that makes this happen (possibly a reduced down one?) - that would be ideal. Ie create a new job, get it to fail in this way - then should be easy to find/fix.
Also some more errors from the browser console.