continuous delivery concept overview. continuous integration systems. devops role

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

Upload: eleksdev

Post on 07-Jan-2017

1.907 views

Category:

Software


4 download

TRANSCRIPT

Page 1: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

eleks.com eleks.com

Continuous Delivery concept overview, Continuous Integration SystemsDevOps role

Eleks Engineering Camp

Page 2: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

eleks.com

What is DevOps

What is DevOps?What is DevOps?

Page 3: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

DevOpsDevOps 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.

Page 4: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

Why DevOps?

Page 5: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role
Page 6: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role
Page 7: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

Continuous IntegrationContinuous 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.

Page 8: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

Maintain a single source repositoryAutomate the buildMake your build self-testingEvery commit should build on an integration

machineKeep the build fastTest in a clone of the production environmentMake it easy for anyone to get the latest

executableEveryone can see what’s happeningAutomate deployment

Continuous Integration: the Practices

Page 9: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

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

Page 10: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

It is the practice of releasing every good build to users

Page 11: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

TeamCityUser friendly interfaceLow entry pointEasy to useFree for open source projects. Has limited free

version for others.

Page 12: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

JenkinsCompletely freeHighly extensibleUpdates rapidlyOpen source

Page 13: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

DEMO

Page 14: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

QUESTIONS?

Page 15: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

Useful linkshttp://ss64.com/ - Command line referencehttp://visualstudioshortcuts.com/https://msdn.microsoft.com/en-us/library/

ms164311.aspx - MSBuild referencehttp://www.sonarqube.org/downloads/ - code

analysis tool

Page 16: Continuous Delivery concept overview. Continuous Integration Systems. DevOps role

eleks.com

Making Innovation Happen