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

Editing job configuration throws Serialization Error

    Details

    • Similar Issues:

      Description

      Hello,

      I've created a job which works fine. Then I decided to generate reports in the "Finalize run" step. But I can't edit it anymore: when I clicked on "Save" after configuring the report, Jenkins threw an exception. From this time, any trivial change will throw this exception. (stack in attachments)
      My job still works but I can't change anything about it. The only way I can change anything except the reporting options is cloning the job and configure the clone.
      I've reproduced the bug with both "Generate report" and "Export report" options.

      Something I want to mention about my project's architecture: I have my ZAP jar, zap.sh and ZAP config files within my jenkins/tools/hudson.task.Ant_AntInstallation. I put them there because Jenkins was complaining he couldn't find them here.

        Attachments

          Activity

          Hide
          jordangs Goran Sarenkapa added a comment - - edited

          Hi Zoé Thivet, I have verified that this is indeed a bug, however i currently cannot determine the cause as it seems random. If i press apply or save multiple times or at worst, I restart Jenkins, the issue will go away.

          Currently we are on version 1.0.8 and focusing on adding some new features as well as hot fixes. The issue may be because I've upgraded from JDK 7 to 8 but I'm ignoring some errors. So I'll add it as a 1.1.0 milestone as code cleanup and i'll follow up the issue with Jenkins members to see if they have any idea why the serialization is failing.

           

          Referencing additional documentation Google Group:

          https://groups.google.com/forum/#!topic/zaproxy-jenkins/jETpNSMPx8Q

          Show
          jordangs Goran Sarenkapa added a comment - - edited Hi Zoé Thivet , I have verified that this is indeed a bug, however i currently cannot determine the cause as it seems random. If i press apply or save multiple times or at worst, I restart Jenkins, the issue will go away. Currently we are on version 1.0.8 and focusing on adding some new features as well as hot fixes. The issue may be because I've upgraded from JDK 7 to 8 but I'm ignoring some errors. So I'll add it as a 1.1.0 milestone as code cleanup and i'll follow up the issue with Jenkins members to see if they have any idea why the serialization is failing.   Referencing additional documentation Google Group: https://groups.google.com/forum/#!topic/zaproxy-jenkins/jETpNSMPx8Q

            People

            • Assignee:
              jordangs Goran Sarenkapa
              Reporter:
              zoe_thivet Zoé Thivet
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: