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

Parametrized publishing can no longer be configured

    XMLWordPrintable

Details

    Description

      With jenkins version 2.106 and cifs publisher version 0.6, I can no longer configure parametrized publish. I always get an error

      org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.plugins.publish_over.ParamPublish
      	at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265)
      	at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:764)
      	at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83)
      	at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)
      Caused: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.plugins.publish_over.ParamPublish from {"parameterName":"IS_M2RELEASEBUILD"}
      	at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:680)
      	at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478)
      	at org.kohsuke.stapler.RequestImpl.injectSetters(RequestImpl.java:833)
      	at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:783)
      	at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83)
      	at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)
      Caused: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.plugins.publish_over_cifs.CifsPublisherPlugin [...]

      as soon as I enable the checkbox.

      It also happens when I downgrade to cifs publisher 0.3.

      I can not exactly tell from which jenkins version this occurs - I had the build jobs configured with parametrized publish for some months without any change, but since upgrading from 2.96 to 2.102 three weeks ago, the publish step was silently removed from all my jobs (I just noticed today).

      Attachments

        Activity

          As there was no reaction here for some time, I suspect the auto assignment to a user bap who has not activity for some years now might not be intented... Please excuse me if I came to the wrong conclusion.

          mcnetic Nicolai Ehemann added a comment - As there was no reaction here for some time, I suspect the auto assignment to a user bap who has not activity for some years now might not be intented... Please excuse me if I came to the wrong conclusion.
          slide_o_mix Alex Earl added a comment -

          I just took over maintaining the publish over plugins recently and reassigned the issues to myself. I am working through them as I can.

          slide_o_mix Alex Earl added a comment - I just took over maintaining the publish over plugins recently and reassigned the issues to myself. I am working through them as I can.
          thebroth The Broth added a comment -

          Same issue on Jenkins 2.107.1 with Publish Over CIFS 0.9

          thebroth The Broth added a comment - Same issue on Jenkins 2.107.1 with Publish Over CIFS 0.9
          bdenys Bruno D. N. added a comment - - edited

          Environment:

          • Jenkins: v. 2.19.4 on Windows Server 2012 R2
          • plugin publish-over: v. 0.21
          • plugin publish-over-cifs: v0.9

          Scenario:
          there already exists a Jenkins job which makes use of the publish-over-cifs plugin. A new job needs to be created by copying the existing job. The only parameter to change is the name of the CIFS-share to which an artifact needs to be copied.

          1. create a new Jenkins job by copying it from an existing Jenkins job which copies artifacts to a CIFS share
          2. change the name of the target CIFS share
          3. save the Jenkins job

          Result:
          the above error appears

          Unsuccessfull workaround:
          it was not possible to change the XML-file of the newly created Jenkins job (which contained the target CIFS-directory of the original Jenkins job).

          Successfull workaround:
          create the Jenkins job from scratch.

          bdenys Bruno D. N. added a comment - - edited Environment: Jenkins: v. 2.19.4 on Windows Server 2012 R2 plugin publish-over : v. 0.21 plugin publish-over-cifs : v0.9 Scenario: there already exists a Jenkins job which makes use of the publish-over-cifs plugin. A new job needs to be created by copying the existing job. The only parameter to change is the name of the CIFS-share to which an artifact needs to be copied. create a new Jenkins job by copying it from an existing Jenkins job which copies artifacts to a CIFS share change the name of the target CIFS share save the Jenkins job Result: the above error appears Unsuccessfull workaround: it was not possible to change the XML-file of the newly created Jenkins job (which contained the target CIFS-directory of the original Jenkins job). Successfull workaround: create the Jenkins job from scratch.
          slide_o_mix Alex Earl added a comment -

          I'll try and roll out a fixed version for this soon. I'll need to cherry pick some other edits so I don't break things completely. 

          slide_o_mix Alex Earl added a comment - I'll try and roll out a fixed version for this soon. I'll need to cherry pick some other edits so I don't break things completely. 

          Code changed in jenkins
          User: Alex Earl
          Path:
          src/main/java/jenkins/plugins/publish_over/ParamPublish.java
          http://jenkins-ci.org/commit/publish-over-plugin/ce68dcdfb51a20d2ffc98ffa81adb5506730e317
          Log:
          Fix JENKINS-49553

          Add @DataBoundConstructor

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Alex Earl Path: src/main/java/jenkins/plugins/publish_over/ParamPublish.java http://jenkins-ci.org/commit/publish-over-plugin/ce68dcdfb51a20d2ffc98ffa81adb5506730e317 Log: Fix JENKINS-49553 Add @DataBoundConstructor
          slide_o_mix Alex Earl added a comment -

          This is fixed with publish-over-0.22 released a few days ago.

          slide_o_mix Alex Earl added a comment - This is fixed with publish-over-0.22 released a few days ago.

          For your information, all publish-over-cifs component type JENKINS issues related to the Publish Over CIFS plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues

          Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues/79
          And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-49553%22

          (Note: this is an automated bulk comment)

          gmcdonald Gavin McDonald added a comment - For your information, all publish-over-cifs component type JENKINS issues related to the Publish Over CIFS plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-cifs-plugin/issues/79 And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-49553%22 (Note: this is an automated bulk comment)

          People

            slide_o_mix Alex Earl
            mcnetic Nicolai Ehemann
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: