OK, so here are two diagrams that show pipeline statuses for all the
situations I'm aware of after reading the documentation. My comments for
the diagrams:
1) I assumed trigger type doesn't matter at all.
2) PipelineNotificationService / Pipeline / Stage are not names of classes
but abstract
On Mon, Jun 19, 2017 at 9:39 AM, Krzysztof Szatan wrote:
> On 19 June 2017 at 14:42, Aravind SV wrote:
>
>> My question would be: When do you send a "pipeline-status" *notification*?
>> Let's assume three stages, with the third stage being manual. Do
On 19 June 2017 at 14:42, Aravind SV wrote:
> My question would be: When do you send a "pipeline-status" *notification*?
> Let's assume three stages, with the third stage being manual. Do you send
> one as soon as the second stage completes, because the third is manual?
My question would be: When do you send a "pipeline-status" *notification*?
Let's assume three stages, with the third stage being manual. Do you send
one as soon as the second stage completes, because the third is manual? Do
you then send another one for the *same pipeline instance* when the third
Hi!
On 19 June 2017 at 03:02, 'Ashwanth Kumar' via go-cd wrote:
> On the pipeline-status notification. I guess it's not straight forward
> because if a job fails the entire stage fails but an operator can choose to
> ignore that stage and move the pipeline to the next