You can create two pipeline jobs and have the first one trigger the second one
as a downstream job.
i.e in a finally block you can check the result of the build and trigger the
pipeline that publish to nexus
On January 10, 2019 5:30:03 PM GMT+02:00, Faad Sayaou <faad...@gmail.com> wrote:
>I was thinking maybe doing something like this would help but
>unfortunately
>not
>
>node {
>stages....
>
>}
>
>node2 {
>
>stages....
>
>}
>
>
>but it is viewed by jenkins as a single pipeline. I am using the
>scripted
>pipeline syntax
>
>On Thursday, 10 January 2019 16:25:11 UTC+1, Faad Sayaou wrote:
>>
>> Hi everyone,
>> I have this scenario i would like to implement but i don not know if
>that
>> is possible within a single jenkinsfile.
>> My idea was to have 2 pipelines
>>
>> 1st pipeline
>> -git checkout
>> -build
>> -Test
>>
>> 2nd pipeline
>>
>> if first build from the first pipeline was successful, then
>>
>> -re-do the first 3 stages from 1st pipeline
>> -zip the build results
>> -and push to nexus
>>
>> ..is this however feasible within a single jenkinsfile?
>>
>> 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-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>https://groups.google.com/d/msgid/jenkinsci-users/0a680aab-e762-45f4-bd74-7098f5977afa%40googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
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 this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/97F68F8F-DB51-4C09-B894-D8A57A30DFB0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
