Breaks totally when trying to find the responsible committer
See original GitHub issueIt seems I have a job with some strange history on my Jenkins, which wasn’t a problem before updating to 1.12+build.201809061734
(from 1.12+build.201805070054
). The build monitor only shows an error dialog and the background AJAX requests fails with this:
[...]
Caused by: org.codehaus.jackson.map.JsonMappingException: hudson.model.FreeStyleBuild cannot be cast to org.jenkinsci.plugins.workflow.job.WorkflowRun (through reference chain: com.smartcodelt
d.jenkinsci.plugins.buildmonitor.api.Success["data"]->java.util.ArrayList[43])
at org.codehaus.jackson.map.JsonMappingException.wrapWithPath(JsonMappingException.java:218)
at org.codehaus.jackson.map.JsonMappingException.wrapWithPath(JsonMappingException.java:197)
at org.codehaus.jackson.map.ser.std.SerializerBase.wrapAndThrow(SerializerBase.java:166)
at org.codehaus.jackson.map.ser.std.StdContainerSerializers$IndexedListSerializer.serializeContents(StdContainerSerializers.java:127)
at org.codehaus.jackson.map.ser.std.StdContainerSerializers$IndexedListSerializer.serializeContents(StdContainerSerializers.java:71)
at org.codehaus.jackson.map.ser.std.AsArraySerializerBase.serialize(AsArraySerializerBase.java:86)
at org.codehaus.jackson.map.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:446)
at org.codehaus.jackson.map.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:150)
at org.codehaus.jackson.map.ser.BeanSerializer.serialize(BeanSerializer.java:112)
at org.codehaus.jackson.map.ser.StdSerializerProvider._serializeValue(StdSerializerProvider.java:610)
at org.codehaus.jackson.map.ser.StdSerializerProvider.serializeValue(StdSerializerProvider.java:256)
at org.codehaus.jackson.map.ObjectMapper._configAndWriteValue(ObjectMapper.java:2575)
at org.codehaus.jackson.map.ObjectMapper.writeValueAsString(ObjectMapper.java:2097)
at com.smartcodeltd.jenkinsci.plugins.buildmonitor.api.Respond.withSuccess(Respond.java:15)
at com.smartcodeltd.jenkinsci.plugins.buildmonitor.BuildMonitorView.fetchJobViews(BuildMonitorView.java:142)
at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
[...]
I know this is a data problem, but probably there can also be a check in the build-monitor for this.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Tired Of Being Let Down? How To Hold People Accountable
Whatever you do, don't shy away from having the tough conversations like holding people accountable for broken promises. When you fail to do ......
Read more >What's In the Inflation Reduction Act?
Inflation Reduction Act Summary ; Total, Spending and Tax Breaks, -$485 billion ; Health Savings, $322 billion.
Read more >Broken windows theory | Description & Results | Britannica
broken windows theory, academic theory proposed by James Q. Wilson and George Kelling in 1982 that used broken windows as a metaphor for...
Read more >Section 2. Developing Facilitation Skills - Community Tool Box
Learn how to plan well, keep members involved, and create real leadership opportunities in your organization and skills in your members.
Read more >The Declaration of Independence: A History | National Archives
Moving Toward Independence; The Committee of Five ... The Congress gradually took on the responsibilities of a national government.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Would it be possible to just skip the jobs with parsing errors instead of “screwing up” the whole board? Thanks.
Disabling “Display committers” fixed it for me also.