3. THIS IS ME
Tomas Jansson
Manager & Group Lead .NET
BEKK Oslo
@TomasJansson
tomas.jansson@bekk.no
github.com/mastoj
blog.tomasjansson.com
5. WHY CONTINUOUS DEPLOYMENT?
Bug impact
Money
Time
Shorter time between releases
smaller impact
New features faster you
can save or make money
faster
Automated deploy more
time for development
6. WHERE SHOULD I START?
Visualize what is needed for you to make a complete deployment
Ex:
Build
Test
(5 min)
(5 min)
Provision
server
(1 hr)
Deploy
(20 min)
Then ask the following question:
•
How often do I do each step during a day/week/month?
My guess is; build, test, deploy and last provision of server
17. SUMMARY
•
Continuous deployment doesn’t have to be hard
•
The right tools will help you a long way (TeamCity and Octopus deploy)
•
Learn PowerShell, it will make your life easier
18. RESOURCES
Blog post about the setup: http://tinyurl.com/PowerOctoTeam
Octopus Deploy: http://www.octopusdeploy.com
TeamCity: http://www.jetbrains.com/teamcity/
GitHub project: https://github.com/mastoj/OctoWebSetup
NuGet download: https://nuget.org/packages/OctoWebSetup/
Minimizeimpactofbugs long lead time thebugswill have more affect and youneed to take more seriousdecisionaboutwhat to doMinimize time for fix automated (fast) deploy makes it easier to release a fix fasterMore time for whatyouaresupposed to do