Status: Closed (View Workflow)
When using SVN, Jenkins provides a folder named "trunk" inside which the workspace lives. As typically to MVN, inside that folder there lives the "target" output folder.
When publish-over-cifs shall copy files from "trunk", one must actually write "**/trunk" or the plugin won't find "trunk". So far so good. But it creates a "target" folder on the CIFS share then.
To get rid of that, one must cut the "trunk" prefix. But, strange but true, one cannot simply write "trunk", but the prefix must be given as "trunk/target", which is really weird, as
again "trunk" is NOT part of the workspace, but part of the Jenkin's own internals.
Is it possible to echo something in a jenkins maven-type job without modifying the POM?
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/56
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-cifs-plugin/issues?q=%22JENKINS-21908%22
(Note: this is an automated bulk comment)
This issue has been closed - please see the new Github Issue for this in the previous comment.
If you echo $WORKSPACE in your job, what do you get?