urce code.
>
>
>
>
>
> *From:* jenkins...@googlegroups.com <
> jenkins...@googlegroups.com > *On Behalf Of *Felix Dorner
> *Sent:* May 19, 2020 8:47 AM
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: Pull two repos into one build
>
>
>
Hi Mark, I should have mentioned this is a new pipeline not my original SCM
one ( which as you say has an implicit checkout )
On Tuesday, 19 May 2020 15:58:03 UTC+1, Mark Waite wrote:
>
> Glad you're using Jenkins and declarative pipeline. You may want to spend
> an hour watching a
jenkinsfile is also into the CI repos so I can update my C and
apply it on any version of the source code.
From: jenkinsci-users@googlegroups.com On
Behalf Of Felix Dorner
Sent: May 19, 2020 8:47 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Pull two repos into one build
I used
Glad you're using Jenkins and declarative pipeline. You may want to spend
an hour watching a Declarative Pipeline video that Kohsuke Kawaguchi hosted
with Tyler Johnson and me presenting some ideas that make it easier to
succeed with declarative pipeline.
Specific comments are placed inline.
On
Hi Felix, thanks for replying I think I have a steep learning curve ahead
learning this scripting syntax - I've been a paid programmer / analyst /
developer / software engineer for 35 + years but I've never had to use
Jenkins or its ilk - I have to say it's a cool piece of kit
On Tuesday, 19
Hi Mark, thanks for replying I should of mentioned I'm a newbie to Jenkins
so your examples are a tad overwhelming :-) I actually got Jenkins to build
successfuly but it aint pretty.
pipeline{
> agent any
> environment {
> APIproject = "./MyAPI//API.csproj"
>
I used
options { skipDefaultCheckout() }
and then clone my projects into subdirectories with:
checkout([$class: 'GitSCM',
branches: [[name: "*/${env.BRANCH_NAME}"]],
doGenerateSubmoduleConfigurations: false,
extensions: [[$class: 'RelativeTargetDirectory',
relativeTargetDir: subdir1],
]]
That's a very reasonable way of doing things. Be sure that the checkout of
the additional repository is performed in a different directory than the
original checkout. For example, it could be in a new subdirectory inside
the original checkout directory or it could be in another workspace.
Title says it all really - I have an existing Pipeline SCM job setup which
utilises a Jenkins file in my Github repo ( the Jenkinsfile is itself a
pipeline ) All works perfectly.
I want to split my current repo ( seperation of concerns reasons ) into two
repos but still use the Jenkinsfile to
