-
Bug
-
Resolution: Fixed
-
Major
Although it shouldn't happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. This can fail the whole persistence of the flow graph, causing loss of data.
Instead we should intercept and filter out unserializable inputs when the action is created.
- is related to
-
JENKINS-50020 CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
-
- Closed
-
-
JENKINS-50632 JEP-200 - Refusing to marshal org.apache.maven.model
-
- Closed
-
-
JENKINS-50670 Pipeline job does not fail when serialization of Pipeline steps arguments fails within NonCPS
-
- Closed
-
- relates to
-
JENKINS-50633 JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
-
- Resolved
-
- links to
[JENKINS-50752] ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input
Description | Original: Although it *shouldn't* happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. |
New:
Although it *shouldn't* happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. This can fail the whole persistence of the flow graph. Instead we should intercept and filter out unserializable inputs when the action is created. |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Description |
Original:
Although it *shouldn't* happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. This can fail the whole persistence of the flow graph. Instead we should intercept and filter out unserializable inputs when the action is created. |
New:
Although it *shouldn't* happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. This can fail the whole persistence of the flow graph, causing loss of data. Instead we should intercept and filter out unserializable inputs when the action is created. |
Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Summary | Original: ArgumentsAction Should Deal With Unserializable Arguments | New: ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "workflow-cps-plugin #220 (Web Link)" [ 20410 ] |
Remote Link | New: This issue links to "workflow-api-plugin #68 (Web Link)" [ 20411 ] |