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

    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

          mkarg Markus KARG created issue -
          rtyler R. Tyler Croy made changes -
          Field Original Value New Value
          Workflow JNJira [ 153909 ] JNJira + In-Review [ 178648 ]
          slide_o_mix Alex Earl made changes -
          Assignee bap [ bap ] Alex Earl [ slide_o_mix ]
          slide_o_mix Alex Earl added a comment -

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

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

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

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

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

          slide_o_mix Alex Earl added a comment - I'm not sure, I've never used a maven type job.
          slide_o_mix Alex Earl made changes -
          Assignee Alex Earl [ slide_o_mix ]

          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)

          gmcdonald Gavin McDonald added a comment - 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.

          gmcdonald Gavin McDonald added a comment - This issue has been closed - please see the new Github Issue for this in the previous comment.
          gmcdonald Gavin McDonald made changes -
          Resolution Incomplete [ 4 ]
          Status Open [ 1 ] Closed [ 6 ]

          People

            Unassigned Unassigned
            mkarg Markus KARG
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: