Feature request: Make an initial wait for environment status before deploy
See original GitHub issueSometimes when we deploy, the environment isn’t ready yet, because a previous deploy is also running.
It would be awesome with something similar to wait_for_deployment
, but where it waits before deploying too.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Show deployment status in the environment page - GitLab
This is taking into account that we only show 1 status on an environment. Meaning that if the latest deployment was canceled we...
Read more >Deployment policies and settings - AWS Elastic Beanstalk
AWS Elastic Beanstalk provides several options for how deployments are processed, including deployment policies (All at once, Rolling, Rolling with ...
Read more >Set up staging environments - Azure App Service
Deploying an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up...
Read more >EVERYTHING you NEED to know about GitHub Actions ...
The features everyone was waiting for in GitHub Actions are finally here: Environments and Manual App... Tagged with github, deploy, devops, ...
Read more >Monitor Deployments - Salesforce Help
If a validation completed successfully in the last 10 days, and all tests passed with sufficient code coverage, you can perform a quick...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Perfect @einaregilsson. I don’t have much time either, but now the OS community knows how to do this, in case you don’t have time as well. Perfect, thanks.
Hmmm. Might be a good idea. I’d probably have it as a number instead, like
wait_for_deployment_max_seconds
and give it a default of 20 or so. That way you could say that you wanted to wait for a max of maybe 2-3 minutes, since this waiting is eating up your github minutes.