Is deploying your application to production a chore? What about deploying to development or test environments? Those deployments are as important as, if not more than, production. Does your process involve a multi-page Word doc? Are you sure those steps are up to date?
If you or your team has room for improvement in your build and deploy process, then this is the session for you.
In this session, we'll configure a CI/CD pipeline for an existing application. We'll start with build scripts that can run on both developer machines and a build server. Then, we'll configure a build server to build our code and run tests. Finally, we'll wrap it up with configuring push-button deployments from development to production.
- Build Scripts (Cake/FAKE)
- Continuous Integration / Build Automation Server (Appveyor/Azure DevOps)
- Continuous Delivery / Deployment Automation Server (Octopus Deploy)
I work with some of Octopus Deploy's largest customers to help them be successful in their continuous delivery efforts. I'm also active in the broader Octopus community answering questions in Slack, recording videos for our Ask Octopus series, and visiting conferences and user groups to speak about CI/CD and Octopus Deploy.
Before joining the Customer Success team at Octopus, I was a developer and happy Octopus Deploy user. I've always taken an interest in improving processes and automating tasks where possible. This naturally led me to CI/CD and a several phase project to improve my team's build and deploy pipeline. By the end, we had a fully automated build and deploy process that integrated with our other tools through APIs. We even had recurring scheduled deployments to keep our test and demo environments up to date.
Outside of developing and advocating, I perform comedy around Dallas, belong to two needy cats, and like to travel to new places and sample their vegan food.