Continuous Integration With Jenkins

View DevOps course details at www.edureka.co/devops

DevOps: Continues integration with Jenkins

www.edureka.co/devops

Objectives

At the end of this module, you will be able to

Introduction of DevOps

DevOps Life cycle

Different stages in DevOps

Continuous Integration

Introduction to Jenkins

Demo on Jenkins


What is DevOps

DevOps is a software development method that stresses communication, collaboration and integration betweenSoftware developers and information technology ( Operations ) professionals to enable rapid evolution of products or services.


Development & Operation (DevOps)

“Dev” is used as a shorthand for developers inparticular, but in practice it is even wider and itmeans that “all the people involved indeveloping the product,” that include theproduct, QA, and other kinds of disciplines

“Ops” is a blanket term for systems engineers,system administrators, operations staff, releaseengineers, DBAs, network engineers, securityprofessionals and various other sub-disciplinesand job titles”


Development & Operation (DevOps)

DEVOPS

Development

(Software Engineering)

Quality Assurances

Technical Operations


Roles of Developers :

Add or modify features

Try with new technologies

Roles of Operations :

Create stability

Create or enhance services

Development & Operation

Slide 7Slide 7 www.edureka.co/devops

Why DevOps?

Customers RequirementsDev and

Testing TeamOperations

Gap Between Developers and

Operations


Why DevOps?

Development

Operations

Change

» Developer always looks for changes» They try to implement every new

techniques introduced

» Change is the enemy for Operations» It is not reliable and leads to

instability


Dev Tools Ops Tools

» Difficult to integrate the tools

» Very less interest in learning others tools

» Different implementation of similar tools

Why DevOps?


During Deployment

Send out the artifacts based on the requirement received from clients

Manually hacks the scripts received and changes the configuration files to reflect

changes in production environment leading to bugs leading to recover

Development Operations

Why DevOps?


All the artifacts are fine, the error is because of admin issue. Tester

was given wrong set up

Developer gave faulty artifacts

Development

Operations

Day 1: Loss of Work

Why DevOps?


Developer is working on his machine but he is facing some firewall issue for a local tool because of which he is unable to work

Development

He reaches out to local IT team and they point him to the infrastructure team and finally the issue is resolved

Day 2: Loss of Work

Firewall

Why DevOps?


After deployment ,during testing after few scenario tester sees some anomalies

and raises some defects

Day 3: After Deployment

Operations

developer checks in and figures out that correct DB was not deployed

Development

Why DevOps?


DevOps as the SolutionInstead of seeing these two groups as silos who pass things along but don’t really work together, DevOps recognizes the interdependence of software development and IT operations and helps an organization to produce software and IT services more rapidly, with frequent iterations

DevOps bridges the gap between agile software development and operations


DevOps Skills

DevOps Tools – Ability to administer and customize them

Scripting Skills – Demonstrates the traditional scripting skills to IT operations

Coding Skill – Should possess developer skills in using automation

Process re-engineering Skills – Reflects the holistic view of IT and development as a single system, instead

of two different functions

Skills Products

Linux/Unix Commands & Administration

Shell Scripting Bash, Sed/Awk

Coding Perl, Python, Ruby

Configuration Management Puppet, SaltStack, Chef

Bare Metal Configuration Cobbler, Foreman, PXE, DHCP, DNS

DevOps Skill Matrix


DevOps Cycle


Provisioning Configuration Integration

Load Balancer

WebServer WebServer

DB Master

DB Slave DB Slave

Load Balancer

WebServer WebServer

DB Master

DB Slave DB Slave

DevOps Life Cycle


DevOps Tools

Tools for DevOps can be categorized based on the layer of Automation you choose

Each layer has its own tools to build Automation

Infrastructure Automation 1. Cobbler2. Foreman3. Crowbar

Configuration Management 1. Puppet2. SaltStack3. Chef

Continuous Integration 1. Jenkins, Hudson2. SVN, Git, Perforce3. Ant, Maven

Continuous Deployment 1. Capsitrano2. Custom Tools 3. Yum, Deb, RPM

Monitoring 1. Nagios, Sensu, Zabbix2. Custom Tools


Revision control System 1. Git

2. Cvs3. Subversion

Software Configuration Management 1. Clearcase2. perforce3. Accurev

virtualization management Software 1. Vcentre2. Hyper-V

DevOps Tools (Contd.)


Integration Engineer Cloud Specialist

Automation Engineer Release Engineer

DevOps Roles


The most common DevOps challenges are:

Cultural mindset as “How the typical mindset of people could be taken off “

Transitions as “How quickly an organization can build the skill set and cross train people”

DevOps is not a technical problem, it is a business problem as “stake holders are engaged more often”

DevOps is not about cool tools

Other DevOps Challenges

http://www.edureka.co/devops

“Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible”

– Martin Fowler



At a regular frequency (ideally at every commit), the system is:

Integrated

All changes up until that point are combined into the project

Built

The code is compiled into an executable or package

Tested

Automated test suites are run

Archived

Versioned and stored so it can be distributed as is, if desired

Deployed

Loaded onto a system where the developers can interact with it



Immediate bug detection

No integration step in the lifecycle

A deployable system at any given point

Record of evolution of the project

Continuous Integration - Benefits


Code Repositories

SVN, Mercurial, Git

Continuous Build Systems

Jenkins, Bamboo, Cruise Control

Test Frameworks

JUnit, Cucumber, CppUnit

Artifact Repositories

Nexus, Artifactory, Archiva

Continuous Integration - Tools


Jenkins provide continuous Integration services for software development. It’s container is based on Tomcat and can work with various revision control systems like SVN, CVS, Git, etc.

This originally started as Hudson and then after Oracle’s claim, the name Jenkins was coined

It includes a feature-rich web user interface that provides the ability to trigger builds, customize builds, manage resources, manage plugins, and many other features

Jenkins


Builds can be started by:

» Commit in a version control system

» Scheduling via a cron-like mechanism

» Building when other builds have completed or by requesting a specific build URL

Jenkins (Contd.)


Components of Build


Jenkin Flow


Demo on Jenkins

www.edureka.co/apache-spark-scala-training

LIVE Online Class

Class Recording in LMS

24/7 Post Class Support

Module Wise Quiz

Project Work

Verifiable Certificate

Course Features


Questions


Module 1

» Introduction to DevOps and its Necessities

Module 2

» Understand Common Infrastructure Servers

Module 3

» Implement Automated Installations and Deployments

Module 4

» Understand Performance tuning aspects and basic Security for Infrastructure

Course Topics

Module 5

» Basics of Bash/Python Scripting

Module 6

» Basics of Virtualization and it's Concepts

Module 7

» Monitoring And Logging

Module 8

» The Useful DevOps Tools & Commands

Continuous Integration With Jenkins

Technology

Transcript of Continuous Integration With Jenkins