search

jira-importer / jira-github-issues-cifs

0 stars 0 forks source link

[JENKINS-21908] Truncate prefix expects to get "trunk", which is not part of the Jenkins workspace #33

Open jira-importer opened 10 years ago

jira-importer commented 10 years ago

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.

Originally reported by mkarg, imported from: Truncate prefix expects to get "trunk", which is not part of the Jenkins workspace
  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2022/01/10
jira-importer commented 6 years ago

slide_o_mix:

If you echo $WORKSPACE in your job, what do you get?

jira-importer commented 6 years ago

mkarg:

Is it possible to echo something in a jenkins maven-type job without modifying the POM?

jira-importer commented 6 years ago

slide_o_mix:

I'm not sure, I've never used a maven type job.