Super Charge Your Continuous Integration Deployments. Nikola Gotsev April 26, 2016

Transcription

1 Super Charge Your Continuous Integration Deployments Nikola Gotsev April 26, 2016

2 What is Continuous Integration?

3 Wasn`t that the same as Continuous Deployment?

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

5 Or maybe it was a tool?

6 NO!

7 Continuous Integration is a process and a development practice.

8 Continuous Integration In Depth 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 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 Sitecore User Group Conference Europe and its respective speakers. All rights reserved. 8

9 The most common problem?

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

11 So how do I super charge that?

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

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

14 Rule #2 Branches

15 Rule #2 Branches Make sure you have a development branch you have a release branch you have a master branch you create tags for stable versions you create feature branches as necessary to create a hotfix branch in case you need to modify production code and don`t forget to back integrate it

16 Rule #2 Sample Git Branching Model

17 Rule #3 Always manage your project dependencies! Yes the frontend ones as well!

18 Rule #3 Nugget

19 Rule #3 Nugget

20 Rule #3 Or just your custom code!

21 Rule #3 Frontend Dependencies

22 Rule #3 Frontend Dependencies Never version compiled frontend resources (css, javascipt etc.) into source control. Let the build compile them the same way it does with your code!

23 Rule #4 Tests TestsTests Make your code testable Unit Tests And all the rest

24 Rule #4 Make your Sitecore code testable Use MVC Always depend on abstractions not on implementations Consider using Dependency Injection Frameworks Use ORMs Glass, Fortis, Synthesis etc. Make sure to check out Sitecore.FakeDb

25 Rule #4 Unit Tests

26 Rule #4 All the Rest

27 But most important!

28 Rule #5 Keep your QA content up to date It is important to keep your QA content up to date for regression tests.

29 Rule #6 Continuous Deployments

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

31 Continuously Deploying Items - Serialization Or your custom solution!

32 Continuously Deploying Items Building a Package

33 Continuously Deploying Items Installing the Package Options options options: Sitecore.Ship Automatically installs packages posted via HTTP Sitecore Package Deployer Automatically installs packages from the file system.

34 Continuously Deploying Items - Notes TDS can deploy items and files directly if the build server have access to the web server If item files are deployed with the code deployment. Unicorn can deserialize them without the need of installation

35 Continuously Deploying Items Some Advices 1. Make sure you never deploy content items to higher environments 2. Make sure the default Sitecore items versioned won`t get overridden when deploying 3. Keep a minimum amount of content versioned in source control.

36 Continuous Deployments - Scripting Embrace the scripting!!!! Invest some time to learn PowerShell Script common tasks as DB and Website Backups Script common Sitecore Tasks with Sitecore PowerShell Extensions

37 To Deploy or Not To Deploy?

38 Questions? 38

39 Sponsors will be added later. To ensure all sponsors will be displayed nicely, we will supply a new slide with the sponsors later. You can then replace this slide with the new one. 39

40 Thank