An overview of the advantages to automating the deployment process with Octopus Deploy
- [Instructor] It's important that you release the same code and perform the same actions every time you deploy your application. Every manual step in your process is an opportunity for a mistake, which can lead to a broken app and unhappy customers. If you use a consistent, automated process, you know what code is running in production. Knowing what code is running in production is a key to finding problems. If you don't know for sure who released the last build and what the build contained, troubleshooting gets a lot harder.
Environments need their own configuration, such as connection strings, the environment name, and file share locations. If you need to update these values in your code before releasing to every environment, you risk other changes sneaking into the build. It's best to keep configurations separate from your code, and a good deployment tool should make this easy. Manual process means people need to access servers. If people have access to servers, then you may never really know who changed what when.
If a production issue happens, the first question to ask is, "What changed?" If your process isn't automated, the answer will be, "We have no idea."
- What is Octopus Deploy?
- Working with the Octopus server and tentacles
- Using variables to scope configuration items such as roles and targets
- Installing and configuring Octopus Deploy
- Deploying a sample application
- Configuring a build server, adding a project, and creating a release
- Controlling release flow with life cycles and channels