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

Cannot publish over CIFS from artifact directory using pipeline

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When trying to generate a pipeline script for the publish over CIFS plugin, there are two identical options, both called "Send build artifacts to a windows share".

        

      However, the options for the two are not identical. The first one has an option to "use workspace", and the help says "By default this plugin uses the artifacts directory (where archived artifacts are stored)."

      The second one has no options to choose where the files are taken from, and from the help it is clear that the workspace is always used. When I generate a pipeline script with this one, everything works as expected, but I cannot copy from the artifacts directory.

      So, I would like to try the other one, which allows me to copy from the artifacts directory. However, when I try to generate the pipeline script, the output from  the snippet generator is always just "step <object of type jenkins.plugins.publish_over_cifs.CifsPromotionPublisherPlugin>". 

      So how can I publish over CIFS from the artifacts directory?

       

      Options if I choose the first "send artifacts to a windows share":

       

      And output:

       

      Options if I choose the second one:

      And output:

        Attachments

        1. image-2018-12-05-15-42-53-249.png
          37 kB
          Øyvind R
        2. image-2018-12-05-15-50-07-224.png
          18 kB
          Øyvind R
        3. image-2018-12-05-15-51-40-305.png
          7 kB
          Øyvind R
        4. image-2018-12-05-15-52-34-603.png
          12 kB
          Øyvind R
        5. image-2018-12-05-15-53-04-196.png
          17 kB
          Øyvind R

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          The second option shouldn't be showing up (the one that generates the CifsPromotionPublisherPlugin stuff. It is for use with the promoted builds plugin, which doesn't really work in pipeline from what I remember. The workspace is the only location that items can be published from.

          Show
          slide_o_mix Alex Earl added a comment - The second option shouldn't be showing up (the one that generates the CifsPromotionPublisherPlugin stuff. It is for use with the promoted builds plugin, which doesn't really work in pipeline from what I remember. The workspace is the only location that items can be published from.
          Hide
          godskalk Øyvind R added a comment - - edited

          Alex Earl ok, thanks.  

          Maybe you can help me with another problem: No matter what I put under "sourceFiles", the plugin just copies everything from the workspace to the CIFS share.  I don't want to report this as an issue yet since it seems likely it's just a user error. 

          Here is my pipeline script:

          cifsPublisher(publishers: [[configName: 'Test', transfers: [[cleanRemote: false, excludes: '', flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '', remoteDirectory: "${versionstring}", remoteDirectorySDF: false, removePrefix: '', sourceFiles: 'build_output.txt']], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false]])

           

           Edit: Found the issue for the problem above (JENKINS-52461), and that it is caused by a missing separator character setting. I see that the snippet generator automatically puts [, ]+ as the default now, but for some reason this didn't happen when I generated my script. 

          Show
          godskalk Øyvind R added a comment - - edited Alex Earl ok, thanks.   Maybe you can help me with another problem: No matter what I put under "sourceFiles", the plugin just copies everything from the workspace to the CIFS share.  I don't want to report this as an issue yet since it seems likely it's just a user error.  Here is my pipeline script: cifsPublisher(publishers: [[configName: 'Test', transfers: [ [cleanRemote: false, excludes: '', flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '', remoteDirectory: "${versionstring}", remoteDirectorySDF: false, removePrefix: '', sourceFiles: 'build_output.txt'] ], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false]])    Edit: Found the issue for the problem above ( JENKINS-52461 ), and that it is caused by a missing separator character setting. I see that the snippet generator automatically puts [, ] + as the default now, but for some reason this didn't happen when I generated my script. 

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            godskalk Øyvind R
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: