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

Truncate prefix expects to get "trunk", which is not part of the Jenkins workspace

    XMLWordPrintable

    Details

    • Similar Issues:

      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.

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

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

          Show
          slide_o_mix Alex Earl added a comment - If you echo $WORKSPACE in your job, what do you get?
          Hide
          mkarg Markus KARG added a comment -

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

          Show
          mkarg Markus KARG added a comment - Is it possible to echo something in a jenkins maven-type job without modifying the POM?
          Hide
          slide_o_mix Alex Earl added a comment -

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

          Show
          slide_o_mix Alex Earl added a comment - I'm not sure, I've never used a maven type job.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            mkarg Markus KARG
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: