I have personally seen this happen when the script that we run doesn't flush the output stream (or) buffers the STDOUT.
If you can share some details on the script that's supposed to output some content on STDOUT every 10 seconds. PS: A related discussion <https://groups.google.com/d/msg/go-cd/LOHwmPgEZ8I/Gra4FbhRAgAJ> on running a ruby script was discussed last year on this forum. On Mon, May 8, 2017 at 4:21 PM, Jennifer Beckett <[email protected]> wrote: > Hi all, > > One of my pipeline stages is to run a script to check if an AWS deployment > has completed. It does this by polling for the environment status every 10 > seconds and checking some stuff. > The console log for the stage shows no output until the deployment is > complete whereby is dumps many lines of status checking out at once. > However the script outputs the current status every 10 seconds (you can see > this if you run the script manually). > > Do you have to do something special in scripts to allow gocd access to the > output before the execution completed? > > Thanks > > Jenny > > -- > 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. > -- Ashwanth Kumar / ashwanthkumar.in -- 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.
