[JIRA] (JENKINS-49553) Parametrized publishing can no longer be configured

6 views
Skip to first unread message

en@enlightened.de (JIRA)

unread,
Feb 14, 2018, 11:25:04 AM2/14/18
to jenkinsc...@googlegroups.com
Nicolai Ehemann created an issue
 
Jenkins / Bug JENKINS-49553
Parametrized publishing can no longer be configured
Issue Type: Bug Bug
Assignee: bap
Components: publish-over-cifs-plugin
Created: 2018-02-14 16:24
Environment: Jenkins Version 2.106
Priority: Major Major
Reporter: Nicolai Ehemann

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).

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

en@enlightened.de (JIRA)

unread,
Mar 15, 2018, 3:33:02 AM3/15/18
to jenkinsc...@googlegroups.com

en@enlightened.de (JIRA)

unread,
Mar 15, 2018, 3:34:01 AM3/15/18
to jenkinsc...@googlegroups.com
Nicolai Ehemann commented on Bug JENKINS-49553
 
Re: Parametrized publishing can no longer be configured

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@gmail.com (JIRA)

unread,
Mar 15, 2018, 10:29:03 AM3/15/18
to jenkinsc...@googlegroups.com

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

mobile@thebroth.com (JIRA)

unread,
Mar 19, 2018, 10:12:02 PM3/19/18
to jenkinsc...@googlegroups.com

Same issue on Jenkins 2.107.1 with Publish Over CIFS 0.9

brunodenys@gmail.com (JIRA)

unread,
Apr 3, 2018, 4:11:04 AM4/3/18
to jenkinsc...@googlegroups.com
Bruno De Nys edited a comment on Bug JENKINS-49553
* 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.

brunodenys@gmail.com (JIRA)

unread,
Apr 3, 2018, 4:11:04 AM4/3/18
to jenkinsc...@googlegroups.com

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
    1. change the name of the target CIFS share
    1. 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@gmail.com (JIRA)

    unread,
    Apr 3, 2018, 3:31:03 PM4/3/18
    to jenkinsc...@googlegroups.com

    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. 

    scm_issue_link@java.net (JIRA)

    unread,
    Apr 3, 2018, 3:37:03 PM4/3/18
    to jenkinsc...@googlegroups.com

    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@gmail.com (JIRA)

    unread,
    Apr 6, 2018, 3:38:04 PM4/6/18
    to jenkinsc...@googlegroups.com
    Alex Earl resolved as Fixed
     

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

    Change By: Alex Earl
    Status: Open Resolved
    Resolution: Fixed
    Reply all
    Reply to author
    Forward
    0 new messages