• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • cifs-plugin
    • None
    • jenkins.war in jetty on linux, targeting xpsp3

      Jenkins 1.396 and the latest CIFS (1.1.10)

      I can create and access 1 share (and have for some time) without problems, but when I tried to add a second share, it didn't seem to be persisted.

      I tried adding a <com.slide.hudson.plugins.CIFSShare /> block to the file by hand and restarting Jenkins with no luck.

      If I edit that file by hand, only changing the first declared com.slide.hudson.plugins.CIFSShare, it works as expected.

          [JENKINS-8678] CIFS Plugin only seems to persist one share

          Alex Earl added a comment -

          What version of the plugin are you using? I don't see if in the affected versions field.

          Alex Earl added a comment - What version of the plugin are you using? I don't see if in the affected versions field.

          Mark Walling added a comment -

          Jenkins 1.396 and the latest CIFS (1.1.10)

          Mark Walling added a comment - Jenkins 1.396 and the latest CIFS (1.1.10)

          Mark Walling added a comment -

          I can reproduce from a git checkout and hpi:run.

          Only been into a plugin once before, I'll see if I can dig up a test case or something.

          Mark Walling added a comment - I can reproduce from a git checkout and hpi:run. Only been into a plugin once before, I'll see if I can dig up a test case or something.

          Alex Earl added a comment -

          Changed CIFSShare to have a DataBoundConstructor and then in the configure method of the Descriptor, used bindJSONToList to save off the shares.

          Alex Earl added a comment - Changed CIFSShare to have a DataBoundConstructor and then in the configure method of the Descriptor, used bindJSONToList to save off the shares.

            slide_o_mix Alex Earl
            mwalling Mark Walling
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: