Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
Description
Maybe see https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md for details.
Currently publish-over-cifs does not show up as a top level step and also does not show up as a General Build Step (under step).
Attachments
Activity
I can't seem to get this working. getting a the following error:
WorkflowScript: 21: Missing required parameter: "paramPublish"
getrostt
Alex Koepke
added a comment - - edited I can't seem to get this working. getting a the following error:
WorkflowScript: 21: Missing required parameter: "paramPublish"
getrostt Hi alexkoepke,
could you share your pipeline snippet that is causing the issue?
Thanks
Tobias
Hey getrostt,
Thanks for the quick reply! 
pipeline {
agent any
stages {
stage('Build') {
steps {
bat 'npm run vendorinstall'
bat 'gulp release'
bat 'gulp bs_release'
}
}
stage('Deploy') {
when {
expression {
currentBuild.result == null || currentBuild.result == 'SUCCESS'
}
}
steps {
echo "Deploy start"
cifsPublisher masterNodeName:'', alwaysPublishFromMaster: false, continueOnError: false, failOnError: false, publishers: [[configName: 'Foo', transfers: [[cleanRemote: true, excludes: '**/obj/**,**/node_modules/**,**/_src/**,**/_config/**,**/_sassdocs/**', flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: 'site/root', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '**/*']], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false]]
}
}
}
}
Alex Koepke
added a comment - - edited Hey getrostt ,
Thanks for the quick reply!
pipeline {
agent any
stages {
stage( 'Build' ) {
steps {
bat 'npm run vendorinstall'
bat 'gulp release'
bat 'gulp bs_release'
}
}
stage( 'Deploy' ) {
when {
expression {
currentBuild.result == null || currentBuild.result == 'SUCCESS'
}
}
steps {
echo "Deploy start"
cifsPublisher masterNodeName: '', alwaysPublishFromMaster: false , continueOnError: false , failOnError: false , publishers: [[configName: ' Foo ', transfers: [[cleanRemote: true , excludes: ' **/obj /**,**/ node_modules /**,**/ _src /**,**/ _config /**,**/ _sassdocs /** ', flatten: false , makeEmptyDirs: false , noDefaultExcludes: false , patternSeparator: ' [, ]+ ', remoteDirectory: ' site/root ', remoteDirectorySDF: false , removePrefix: ' ', sourceFiles: ' **/ *']], usePromotionTimestamp: false , useWorkspaceInPromotion: false , verbose: false ]]
}
}
}
}
Hi alexkoepke,
what version of Jenkins and Pipeline are you using? Could you provide me the list of plugins and versions installed?
I tested it this morning with Jenkins 2.89.2 and it worked without an error.
Best regards
Tobias
Hi alexkoepke,
I run into the issue as well. It is related to declarative pipeline. I am still figuring out what exactly goes wrong.
As a workaround you can wrap the cifsPublisher step in a script block
script {
cifsPublisher masterNodeName:'', alwaysPublishFromMaster: false, continueOnError: false, failOnError: false, publishers: [[configName: 'Foo', transfers: [[cleanRemote: true, excludes: '*/obj/,/node_modules/,/_src/,/_config/,/_sassdocs/', flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: 'site/root', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '/']], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false]]
}
or set the parameter to null (that is what happens when the step is called from a scripted pipeline):
cifsPublisher paramPublish: null, masterNodeName:'', alwaysPublishFromMaster: false, continueOnError: false, failOnError: false, publishers: [[configName: 'Foo', transfers: [[cleanRemote: true, excludes: '*/obj/,/node_modules/,/_src/,/_config/,/_sassdocs/', flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: 'site/root', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '/']], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false]]
xx
Hey getrostt,
Thank you so much! I found using
paramPublish:[parameterName:''],
worked as well (without the putting it in a script block.
Next step is to figure out how to bust this out into multiple lines!
Wrapping it in a script block allowed me to break it out in to multiple lines.
Thank you so much,
Alex
Alex Koepke
added a comment - - edited Hey getrostt ,
Thank you so much! I found using
paramPublish:[parameterName:''],
worked as well (without the putting it in a script block.
Next step is to figure out how to bust this out into multiple lines!
Wrapping it in a script block allowed me to break it out in to multiple lines.
Thank you so much,
Alex Code changed in jenkins
User: Alex Earl
Path:
pom.xml
src/main/java/jenkins/plugins/publish_over_cifs/CifsPublisher.java
src/main/java/jenkins/plugins/publish_over_cifs/CifsPublisherPlugin.java
http://jenkins-ci.org/commit/publish-over-cifs-plugin/fcc34c73536a1ce23393192b61c49ae2e6971507
Log:
Merge pull request #7 from getrostt/Bugfix/JENKINS-39344
Fix issue JENKINS-39344
Compare: https://github.com/jenkinsci/publish-over-cifs-plugin/compare/546f020c40fc...fcc34c73536a
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/72
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-39344%22
(Note: this is an automated bulk comment)
Any news? This plugin has many downloads and I don't understand why it doesn't support Pipeline.
It applies also to FTP, Dropbox, SSH, plugins as well.