Helpful, as always, thanks. I will take a look at that.
--
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+unsubscr...@googlegroups.com.
To view t
On Wed, Nov 1, 2017 at 2:36 PM itchymuzzle wrote:
> > 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
> 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 tw
Good point. I would rather have it in the Jenkinsfile. Thanks.
On Fri, Oct 6, 2017 at 5:06 PM, Mark Waite
wrote:
>
>
> On Fri, Oct 6, 2017 at 2:24 PM dandeliondodgeball
> wrote:
>
>> Did this two different ways in the same workspace.
>> ../workspace/Pipeline01/Artifact/my.zip
>> ../workspace/
On Fri, Oct 6, 2017 at 2:24 PM dandeliondodgeball
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
> (
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') {
> On 2. Oct 2017, at 21:13, dandeliondodgeball wrote:
>
> Assuming there is no simple generic solution, what is the best custom
> solution? My first thought would be a script.
>
If this is a scripted pipeline, you can do
dir('repo01code') {
checkout scm
}
--
You received this mes
Default: ../workspace/Pipeline01/
Desired: ../workspace/Pipeline01/repo01code/
Why do I want to do this?
The scripts to build the code, can't live at the same level as the code. I
can have the scripts live some place other then the Pipeline01 workspace,
but then Jenkins doesn't "know" about