Issue Type: Bug Bug
Assignee: bap
Components: publish-over-cifs
Created: 21/Feb/14 9:51 AM
Description:

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.

Environment: Plugin 0.2
Project: Jenkins
Priority: Major Major
Reporter: Markus KARG
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to