Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
-
frank, tethys, christmas, iapetus, 1.0
Description
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
Attachments
Issue Links
- 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
Activity
Field | Original Value | New Value |
---|---|---|
Description |
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). |
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 | JENKINS-35759 [ 171771 ] |
Link |
This issue blocks |
Sprint | tethys [ 161 ] | frank [ 156 ] |
Rank | Ranked higher |
Rank | Ranked higher |
Description |
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. |
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 |
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. |
*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. |
Description |
*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. |
*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. *Solution* |
Priority | Major [ 3 ] | Critical [ 2 ] |
Remote Link | This issue links to "White screen of death (Web Link)" [ 15149 ] |
Sprint | frank [ 156 ] | frank, christmas [ 156, 176 ] |
Rank | Ranked lower |
Rank | Ranked higher |
Link |
This issue duplicates |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Duplicate [ 3 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Sprint | frank, christmas [ 156, 176 ] | frank, tethys, christmas [ 156, 161, 176 ] |
Priority | Critical [ 2 ] | Major [ 3 ] |
Remote Link | This issue links to "Stapler PR 89 (Web Link)" [ 15234 ] |
Link |
This issue relates to |
Labels | rest robustness stapler |
Component/s | core [ 15593 ] | |
Component/s | blueocean-plugin [ 21481 ] | |
Labels | rest robustness stapler | blueocean lts-candidate rest robustness stapler |
Component/s | blueocean-plugin [ 21481 ] |
Status | Reopened [ 4 ] | Open [ 1 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Issue Type | Task [ 3 ] | Bug [ 1 ] |
Assignee | Vivek Pandey [ vivek ] | Jesse Glick [ jglick ] |
Remote Link | This issue links to "core PR 2722 (Web Link)" [ 15284 ] |
Sprint | frank, tethys, christmas [ 156, 161, 176 ] | frank, tethys, christmas, pannonian [ 156, 161, 176, 211 ] |
Assignee | Jesse Glick [ jglick ] | Vivek Pandey [ vivek ] |
Status | In Review [ 10005 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Open [ 1 ] |
Sprint | frank, tethys, christmas, pannonian [ 156, 161, 176, 211 ] | frank, tethys, christmas [ 156, 161, 176 ] |
Sprint | frank, tethys, christmas [ 156, 161, 176 ] | frank, tethys, christmas, iapetus [ 156, 161, 176, 216 ] |
Rank | Ranked higher |
Priority | Major [ 3 ] | Critical [ 2 ] |
Link |
This issue relates to |
Rank | Ranked higher |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Sprint | frank, tethys, christmas, iapetus [ 156, 161, 176, 216 ] | frank, tethys, christmas, iapetus, 1.0 [ 156, 161, 176, 216, 221 ] |
Rank | Ranked lower |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Labels | blueocean lts-candidate rest robustness stapler | blueocean rest robustness stapler |
Remote Link | This issue links to "CloudBees Internal OSS-1824 (Web Link)" [ 18548 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
jamesdumay do you want to write up to the mailing list what your proposed fix could be for this?