--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f6b55274-4823-47e3-b1a7-46892e9d3601%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Fri, Oct 6, 2017 at 2:24 PM dandeliondodgeball <chris...@3derm.com> wrote:Did this two different ways in the same workspace.../workspace/Pipeline01/Artifact/my.zip../workspace/Pipeline01/clonedRepo/One for the artifact I needed.For this I used an attribute in the CopyArtifact plugin, like this (declarative pipeline):stages {
stage('Copy Archive') {
steps {
script {
step ([$class: 'CopyArtifact',
projectName: 'Create_archive',
filter: "packages/my.zip",
target: 'Artifact']);And another for the code which was getting cloned.For this I used the "Check out to sub-directory" feature in the git plugin, like this:
If you use the dir('dest-dir') { checkout scm } syntax, you avoid using that special case from the git plugin, and have something that is maintained in code (and looks like pipeline), rather than something that looks like a special case of the git plugin.The technique you used (with the git extension) works, but was really created to be used with freestyle projects. Pipeline has a better way to do it with the dir() step.Mark Waite
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f6b55274-4823-47e3-b1a7-46892e9d3601%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/ZlxbJHRC2Dg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG_t7%2BvdWK0P1qovNV5zX7J71UEfoWsCxXkHaM8TZH%3D1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
101 Huntington Ave, 17th Floor
Suite
1300 c/o 3Derm @ BCBSMA
Boston, MA 02199
> If you use the dir('dest-dir') { checkout scm } syntax, you avoid using that special case from the git plugin, and have something that is maintained in code (and looks like pipeline), rather than something that looks like a special case of the git plugin.This works, but the code is cloned twice. Once in the workspace, then again into the sub directory defined by dir('dest-dir'), in the same workspace. I assume there is no way around this, as Jenkinsfile needs to be found, to be able to use it. But I figured I would ask. Thanks.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b9acde7c-a050-4b6b-8979-c97a51633959%40googlegroups.com.