Sleep in Pipelines

[wschult]

Hello,

I have a pipeline that needs to wait until a service was successfully deployed. This will take approximately 30 minutes. My question is, is it generally a good idea to use the sleep function within the pipeline to wait and then look periodically if the deployment was successful or is there a better way to do that? What happens with my "bitbucket build minutes"? Does the time where the process is sleeping count to this?

Best,

Wolfgang.

[Denise Skidmore]

If the deployment step can tag the repository when it's done, then you can trigger a pipeline off the tag.

[wschult]

Nice idea , you only have to take care that you don't mess your repro with tags ;-)

[Ankit Gupta]

I think the build minutes are used if you sleep within the pipeline script. 

Is the other service deployed via Bitbucket?

If yes, you could consider running the pipeline as a consequent step to the previous service deployment. This will ensure the ordering. If its a different pipeline you can trigger the other pipeline via a pipe.

If no, you could trigger the pipeline via a POST API after the other service comes up. This would however require a script on the server where the service is running.

[wschult]

Thank you for the answer. Is it possible to trigger a pipeline lets say "in 30 minutes"?

[Ankit Gupta]

I don't think there is feature in Scheduled Pipelines to trigger after a timeout.