So if task A takes about an hour. Wouldn't you want the pipeline to wait
until it completes? That way you know the status of the task isn't? We also
use GoCD as a workflow scheduler and realised over the years that waiting
for the task makes sure we get both history (runtime graph, success
Hi Ashwanth,
Thank you for response. Below is my Usecase:
1. Pipeline A trigger some task which takes time to complete(say 1 hour)
2. Pipeline B have verification steps for pipeline A which needs to wait
for 1 hour
I can have some other way like using AWS lambda but this is the easiest way
what
You can't do that across stages in a single pipeline but you might be able
to do it across pipelines. I'm going to assume pipeline A is the first
pipeline and you want pipeline B to run 2 hours after A has finished.
Here are some possible scenarios:
1. Pipeline A runs on a schedule
If yes, then
Hi All,
i want to give some 1 hour time gap between 2 pipelines/stages. can this be
possible without using sleep as i do not want my agent to engage for this
time duration.
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To unsubscribe from this
