This document discusses continuous integration (CI) processes and practices. It defines CI as maintaining a single source code repository and automating the build and testing process. When code changes are committed, the CI server checks out the code, builds it, and runs unit and integration tests. If the build or tests fail, the CI server alerts the team. The document provides several rules for supercharging a CI process, including always having CI in place, managing dependencies, writing tests, keeping content up to date, and continuously deploying items and code changes. Continuous deployment involves serializing content changes, building packages, and deploying packages to environments.

1. SuperchargeYour
Continuous
Integration
Deployments
Nikola Gotsev
April 26, 2016

2. What isContinuous Integration ?

3. Isn’t that the same asContinuous
Deployment ?

4. Or is it related to the source control
system I use ?

5. Or maybe it is a tool ?

6. NO !

7. Continuous Integration is a process
and a development practice.

8. CI -The Practice
• Maintain a single source repository
• Automate the build
• Make your build self-testing
• Every commit should build on an integration machine
• Make it easy for anyone to get the latest executable
• Everyone can see what’s happening

9. CI -The Process
• Developers check out code into their private workspaces.
• When done, commit the changes to the repository.
• The CI server monitors the repository and checks out changes when they
occur.
• The CI server builds the system and runs unit and integration tests.
• The CI server releases deployable artefacts for testing.
• If the build or tests fail, the CI server alerts the team.
• Continue to continually integrate and test throughout the project.

10. CI -The Process
https://insights.sei.cmu.edu/devops/2015/01/continuous-integration-in-devops-1.html

11. CI -The ProcessSitecore Nightly Build
https://insights.sei.cmu.edu/devops/2015/01/continuous-integration-in-devops-1.html

12. The most common problem?

13. “It is cheaper to find bugs in lower environments. It is really
cheap on a Dev Box and really expensive on Production.”
- CharlesTurano, CTO, Hedgehog Development

14. “Continuous Integration doesn’t get rid of bugs, but it does
make them dramatically easier to find and remove.”
- Martin Fowler, Chief Scientist,ThoughtWorks

15. How do I supercharge myCI Process?

16. Rule #1
Always have a continuous integration build in place!
Scheduled builds count!

17. Rule #1.1
Have an award for whoever broke the build last!

18. Rule #2 Branches

19. Rule #2 Branches
Make sure to …
• … have a master branch
• … have a development branch
• … create tags for production releaases
• … have feature branches for long running features
• … use hotfix branches as necessary

20. Rule #2SampleGit Branching Model
https://backlogtool.com/git-guide/en/stepup/stepup1_5.html

21. Rule #3
Always manage your project dependencies!
Yes the front-end ones as well!

22. Rule #3 Nugget

23. Rule #3 Nugget

24. Rule #3
Or just your custom code !

25. Rule #3 Front-end Dependencies
Bower

26. Rule #3 Front-end Dependencies
Never version compiled front-end resources (css, javascipt
etc.) into source control. Let the build compile them the
same way it does with your C# code!

27. Rule #4 Tests,Tests,Tests

28. Rule #4 Make yourSitecore code testable
• Use MVC 
• Always depend on abstractions not on implementations
• Consider using Dependency Injection frameworks
• Use ORMs – Glass, Fortis, Synthesis
• Make sure to try Sitecore.FakeDb

30. Rule #4UnitTests

31. Rule #4 IntegrationTests -Selenium

32. Takeaway

33. Rule #5 Keep your content up to date
Sitecore PowerShell Extensions

34. Rule #6Continuous Deployments

35. Continuously Deploying Items
Usually a 3 step process:
1. Find a way to serialize your items and bring them to
source control
2. Build a package out of your serialized items
3. Deploy the package to the environment

36. Continuously Deploying Items-Serialization
Or your custom solution !

37. Continuously Deploying Items – Building a Package
Sitecore Courier

38. ContinuouslyDeployingItems – Installingthe Package
• Sitecore.Ship – Automatically installs packages posted
via HTTP
• Sitecore Package Deployer – Automatically installs
packages from deployed on the file system

39. Continuously Deploying Items- Notes
• TDS can deploy items directly(without a need for
packaging), if the build server has access to the
webserver file system
• Unicorn can deserialize deployed serialized items
without the need for packaging

40. Continuously Deploying Items–SomeAdvices
1. Keep a minimum amount of content versioned in source
control
2. Never deploy content and media to higher
environments, use tools or packages to move them
3. Always backup the databases before deploying items

41. Continuous Deployments -Scripting
• Embrace the scripting !!!!
• Invest some time to learn PowerShell
• Script common tasks as DB andWebsite Backups
• Script common SitecoreTasks with Sitecore PowerShell
Extensions

42. Production-To Deploy or NotTo Deploy?

43. My perfect production build scenario
1. Clean Code Checkout
2. Restoring NuGet Packages
3. Restoring and Recompiling Frontend Assets
4. Running UnitTests (Integration – lower environments)
5. Automated PowerShell backups (Remote Execution)
6. Building CM and CD Packages
7. Deploy and install the packages (install can be manual)

44. Questions?
44

45. Thank you!
ngotsev@hhogdev.com
@nsgocev
http://sitecorecorner.com