I have ci
, so our staging environment builds itself.
Should I have a script that not only builds production but does all the branching for it as well?
When you have one code base on two different urls with skinning, should they be required to build at once?
Deployment automation is what enables you to deploy your software to testing and production environments with the push of a button. Automation is essential to reduce the risk of production deployments.
Automated Deployment is a practice that allows you to ship code fully or semi-automatically across several stages of the development process - from initial development right through to production. It contributes to more efficient and reliable deployments.
Minimal errors Deployments that are automated are much less error-prone compared to manual deployments. Unfortunately, manual deployments involve multiple steps and can lead to human error.
Automate your deployment processDeployment automation reduces errors, speeds up deployments, and makes the process so easy, practically anyone on your team can do it. The simplest form of deployment automation is the use of scripts to deploy specific actions in a specific environment in a specific context.
The only way to be too automated is if you are spending more time fighting with building or fixing automation scripts than you would just doing the job manually. As long as your automation scripts take less time and produce fewer errors than doing the job manually, then automation is great.
Scripts to build and branch for production are a great idea!
In my opinion anything the computer is capable of doing automatically it should do, because it can do it faster, easier and without thought from you. Within reason of course, but stuff like that can be very trivial to automate, so I've always been a proponent of automating that whole process.
and plus it can be fun too!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With