You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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.
Thank you for the answer. Is it possible to trigger a pipeline lets say "in 30 minutes"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think there is feature in Scheduled Pipelines to trigger after a timeout.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.