Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59020

Fix java.io.NotSerializableException: JiraDeploymentInfoResponse

      The following issue has been reported regarding the jiraSendDeploymentInfoStep:

       

      Caused: java.io.NotSerializableException: com.atlassian.jira.cloud.jenkins.deploymentinfo.service.JiraDeploymentInfoResponseCaused: java.io.NotSerializableException: com.atlassian.jira.cloud.jenkins.deploymentinfo.service.JiraDeploymentInfoResponse at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:926) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040) 
      ...
      

      The underlying root cause seems to be the fact that the step return is not serializable (doesn't implement the Serializable interface)

          [JENKINS-59020] Fix java.io.NotSerializableException: JiraDeploymentInfoResponse

          Rafal Myslek created issue -
          Rafal Myslek made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Rafal Myslek made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Rafal Myslek made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Rafal Myslek made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Rafal Myslek made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            rafalmyslek Rafal Myslek
            rafalmyslek Rafal Myslek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: