DevOps is a culture and practice that aims to rapidly build, test, and release software. Continuous integration requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by automated builds to detect problems early. Continuous delivery is the practice of releasing every good build to users. Popular tools for continuous integration include TeamCity, Jenkins, and others.

1. eleks.comeleks.com
Continuous Delivery concept overview,
Continuous Integration Systems
DevOps role
Eleks Engineering Camp

2. eleks.com
What is DevOps
What is DevOps?
What is DevOps?

3. DevOps
DevOps is a culture, movement or practice, which aims at
establishing a culture and environment where building,
testing, and releasing software, can happen rapidly,
frequently, and more reliably.

4. Why DevOps?

7. Continuous Integration
Continuous Integration (CI) is a development practice that
requires developers to integrate code into a shared
repository several times a day. Each check-in is then
verified by an automated build, allowing teams to detect
problems early.
By integrating regularly, you can detect errors quickly,
and locate them more easily.

8. Maintain a single source repository
Automate the build
Make your build self-testing
Every commit should build on an integration machine
Keep the build fast
Test in a clone of the production environment
Make it easy for anyone to get the latest executable
Everyone can see what’s happening
Automate deployment
Continuous Integration: the Practices

9.  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.
 The CI server assigns a build label to the version of the code it just built.
 The CI server informs the team of the successful build.
 If the build or tests fail, the CI server alerts the team.
 The team fix the issue at the earliest opportunity.
 Continue to continually integrate and test throughout the project.
Continuous Integration: How to do it

10. It is the practice of releasing every good build to users

11. TeamCity
User friendly interface
Low entry point
Easy to use
Free for open source projects. Has limited free version for
others.

12. Jenkins
Completely free
Highly extensible
Updates rapidly
Open source

13. DEMO

14. QUESTIONS?

15. Useful links
http://ss64.com/ - Command line reference
http://visualstudioshortcuts.com/
https://msdn.microsoft.com/en-us/library/ms164311.aspx -
MSBuild reference
http://www.sonarqube.org/downloads/ - code analysis tool

16. eleks.com
Making Innovation Happen