Not good at "Passive waiting" means?
On Saturday, November 5, 2016 at 2:20:04 AM UTC+5:30, Jason Whittington wrote: > > GoCD is not good at "passive waiting" which can be a really frustrating > limitation. There are many reasons why you might want to: > > - Start a pipeline > - Notice that an external event needs to happen (like "the server > needs to come online") > - Continue executing > > This isn't a big deal if the event is going to happen in a matter of > minutes but if it is going to take hours then we really need another > mechanism. > > One such mechanism could be: > > - Start a pipeline > - Run automatically until you get to a manual stage, then wait > - *Have an external service trigger the manual stage (hours or days > later)* > - Profit! > > I see that there is an API that does this that has been in the product for > years (per this blog > <http://foldingair.blogspot.com/2014/03/thouthworks-go-asynchronously-trigger.html> > ): > > curl --data "" > http://user:password@server:8153/go/run/uat_start_FullPipelineTest/11/TestingComplete > > <http://GoAgent:mV5bGwvvDP3HZX5B6RZh@vs-bob:8153/go/run/uat_start_FullPipelineTest/10/TestingComplete> > > People have been asking for this to be supported for two years. Can we > get that into an upcoming release? Pretty please? :) > > > > > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
