-
Bug
-
Resolution: Fixed
-
Critical
-
-
frank, tethys, christmas, iapetus, 1.0
Context
If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible.
A good example of this happening is JENKINS-40083.
If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project.
Solution
- blocks
-
JENKINS-39647 Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon
-
- Resolved
-
- duplicates
-
JENKINS-39647 Failed to write defaultParameterValue: IAE from ExtensibleChoiceParameterDefinition.createValueCommon
-
- Resolved
-
- relates to
-
JENKINS-40083 Blueocean fails to show pipelines due to analysis-core failure
-
- Resolved
-
-
JENKINS-41459 Loading never finishes on blue ocean dashboard when clicked show more button.
-
- Closed
-
- links to
[JENKINS-40088] JSON serialization should not fail if a plugins action failed to serialize
Description |
Original:
If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API). |
New:
If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project. |
Epic Link | New: JENKINS-35759 [ 171771 ] |
Link |
New:
This issue blocks |
Sprint | Original: tethys [ 161 ] | New: frank [ 156 ] |
Rank | New: Ranked higher |
Rank | New: Ranked higher |
Description |
Original:
If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project. |
New:
If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project. |
Description |
Original:
If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project. |
New:
*Context* If there is a problem with the serialization of an Action then the rest response should not fail. We are unable to control 1000s of plugins and it would be a shame if a single plugin failed and made Blue Ocean inaccessible. A good example of this happening is If the serialization of an action fails, the logs should identify what plugin failed and link to its wiki page (I believe all of this info is available via the Plugin Manager API) and ask them to report the stack trace as a bug for that project. |
jamesdumay do you want to write up to the mailing list what your proposed fix could be for this?