Hi everyone. thank you all for your wonderful replies.
First of all, I will like to have a two separate pipelines in order to
manage builds from feature branches as well as to make sure the right and
stable version is uploaded to my nexus repository. I tried Denis's approach
by creating two sepa
I agree with Arnaud.
However, having an input means that if you cancel the input, you'll have
aborted the build. So, even if the first 3 steps are successful, you'll
have an aborted build.
You could try/catch the input, but that will complexify the pipeline imo.
Could you explain why you need to
Hi,
Denis answer is good but why are you doing that?
You said if pipeline #1 succeed, you run pipeline #2 which redo same steps
including git checkout then push result to nexus.
But you don't have guarantee that git checkout will fetch same source code.
Why not add input validation on nexus stage
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 wrote:
>I was thinking maybe doi
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 everyon
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
