CodeCampIasi25Oct2014

2. Click’n’Deploy

3. What we want to
achieve

4. Naive deployment approach
Manually change conf ig f iles
Xcopy/Publish web application
Run database scripts
Run scripts to install/update window services
Independent deploy
Repeat for each server and environment

5. Continuous Integration
and
Continuous Deployment

6. Real life example

7. Application Architecture
Multiple Database servers
back-up
Environment Run update script
specif ic
conf iguration
Rollback Install service if needed
using netstat
Back-up current version
Environment specif ic
configuration
Xcopy/FTP/publish
by Radu Pascal & Romulus Crisan

8. Is this ok ?
It’s ok, but:
It can take lots of time
Error prone
No easy way to see deployed version
Rollbacks can be painful
Lack of confidence
Multiply that by the number env.

9. Our approach
Automate, Automate, Automate !!

10. Before we build..

11. Source control
TFS
Git
SVN
Visual Studio Online (TFS in the cloud)
Github
Bitbucket
Lots and lots more…

12. by Radu Pascal & Romulus Crisan

13. by Radu Pascal & Romulus Crisan

14. by Radu Pascal & Romulus Crisan

15. by Radu Pascal & Romulus Crisan

16. Can we build now?

17. Developing with
Visual Studio Online
Team
Foundation
Service
Developer
Visual Studio
by Radu Pascal & Romulus Crisan
Build
Server
Visual Studio Online

18. Team
Foundation
Service
Developer
Visual Studio
by Radu Pascal & Romulus Crisan
Build
Server
Visual Studio Online
Build
Server
On-Premises
Adding On-Premises
Build Server

19. Instal TFS Build Server
Add a VSO user with enough rights to
build
Download TFS/TFS Express
Follow the Wizard

20. Visual Studio Online
Rights for Build
Server User
by Radu Pascal & Romulus Crisan

21. by Radu Pascal & Romulus Crisan
Conf igure Team
Foundation Build
Service

22. by Radu Pascal & Romulus Crisan
Add your Visual
Studio Online
Account

23. Sign into the
repository with a
user with enough
rights..
by Radu Pascal & Romulus Crisan

24. Finish setting The Build Server
- Setup .Net build environment or..
- Install Visual Studio (Express)
- Install any SDKs
- Setup any licenses

25. Time to build..

26. Create a New Build
Definition
by Radu Pascal & Romulus Crisan

27. Create a New Build
Definition
by Radu Pascal & Romulus Crisan

28. Create a New Build
Definition
by Radu Pascal & Romulus Crisan

29. Create a New Build
Definition
by Radu Pascal & Romulus Crisan

30. Create a New Build
Definition
by Radu Pascal & Romulus Crisan

31. Build Definitions
Gated – verify that code is compilable, and
UTs are green
Continuous Integration – above plus
generate deliverables
Scheduled (Nightly) – above plus
Automation Testing, and Automated
Deploys

32. Other Build Servers?
Team City
Cruise Control
Jenkins
.. and don’t forget to create a MSBuild
script

33. Ok, but how we
build a SPA?

34. Task runner
Grunt vs. Gulp
Node.js awesomeness
Pre-compile, concat, uglify, lint, tests
Dev vs Prod

35. Our approach
Automate, Automate, Automate !!

36. Time to deploy..

37. Reasons
As simple as a few clicks..
Fast
Removes lots of human errors
Real time and history information

38. by Radu Pascal & Romulus Crisan

39. Octopus Deploy
Automated deployment for .NET
All your deployments, in one place
Deploy on-premises or to the cloud,
securely
Configuration and scripting
Integrates with your build server

40. Environments

41. Environments
Machine
Tentacles
Types
Roles

42. Octopus and tentacles
With Tentacle
With Tentacle
by Radu Pascal & Romulus Crisan
Azure SQL
Database
Application
Servers
Octopus Server
With Tentacle
Azure
Website

43. Repository

44. Repository
Nuget packages
Internal and external repositories
Versioning:
Semantic versioning (semver.org)
Zero to nine (zero29)

45. Octopus Project

46. Recap
TFS Build
Node.js Task runner
Octopus Deploy

47. Thank you
radupascal.com
&
romuluscrisan.com