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"
> APIPublishPath = "//home//myname//Jenkins//Linux-ARM64//"
> Commonproject = "./Common.csproj"
> CommonPublishPath =
> "//home//myname//Jenkins//Linux-ARM64//Common//"
> }
>
> stages{
> stage('Checkout Common') {
> steps {
> git '[email protected]:myname/Common.git'
> }
> }
>
> stage('Build Common'){
> steps{
> sh "dotnet build ${env.Commonproject} -c Release -r linux-arm64 -o
> ${env.CommonPublishPath}"
> }
> }
> stage('Checkout API') {
> steps {
> dir('API')
> {
> git '[email protected]:myname/API.git'
> }
> }
> }
> stage('Build API'){
> steps{
> sh "dotnet build ${env.APIproject} -c Release -r linux-arm64 -o
> ${env.APIPublishPath}"
> }
> }
> }
> }
>
>
>
> What I had to do which I don't like doing is add a hard coded reference in
> my API.csproj to the Common.dll in my buils output folder - but it works
> and hopefully I'll get some tips on here which will help me achieve this in
> an elegant manner
>
On Tuesday, 19 May 2020 13:34:38 UTC+1, Mark Waite wrote:
>
> 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.
>
> dir('my-subdirectory') {
> checkout .... needed options ...
> }
>
> There are various examples available. I have a scripted pipeline example
> <https://github.com/MarkEWaite/jenkins-bugs/blob/0e5da043baa1249f306fbda2e87cc2fb12ac902f/Jenkinsfile#L18>
> and
> a declarative pipeline example
> <https://github.com/MarkEWaite/jenkins-bugs/blob/576e3ea0e9d9eb93970fe5d144ed86b623c22994/Jenkinsfile#L17>
> (though
> that one uses the outmoded `git` step instead of the modern `checkout`
> step) in case they help you.
>
> Mark Waite
>
> On Tue, May 19, 2020 at 6:13 AM Pete Kane <[email protected]
> <javascript:>> wrote:
>
>> 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 pull them both into one build (
>> does this make sense ? ) is this the correct way of doing things ?
>>
>> TIA
>>
>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/354e3634-2e36-4de8-9664-af47450fe906%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/354e3634-2e36-4de8-9664-af47450fe906%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/438f9439-1f8e-41ae-a537-4fa8da84831f%40googlegroups.com.
