0% found this document useful (0 votes)
39 views34 pages

Continuous Integration (Jenkins) : Ahmed Gomaa

This document discusses continuous integration using Jenkins. It provides an overview of continuous integration, the history and benefits. It then discusses Jenkins in more detail, including its features such as build triggering, source code management, build tools, reporting and security management. The document demonstrates how to configure security in Jenkins and concludes with a question and answer section.

Uploaded by

pankaj boricha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
39 views34 pages

Continuous Integration (Jenkins) : Ahmed Gomaa

This document discusses continuous integration using Jenkins. It provides an overview of continuous integration, the history and benefits. It then discusses Jenkins in more detail, including its features such as build triggering, source code management, build tools, reporting and security management. The document demonstrates how to configure security in Jenkins and concludes with a question and answer section.

Uploaded by

pankaj boricha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 34

Continuous Integration

(Jenkins)

Ahmed Gomaa
22nd Oct 2014
Agenda
• What’s Continuous Integration
• Jenkins
– Features
– Plugin
– Security Management
• Demo
• Q&A
2
What’s Continuous
Integration?
• In software engineering, continuous integration (CI)
implements continuous processes of applying quality
control - small pieces of effort, applied frequently.
Continuous integration aims to improve the quality of
software, and to reduce the time taken to deliver it, by
replacing the traditional practice of applying quality
control after completing all development.

Ref: http://en.wikipedia.org/wiki/Continuous_integration
3
History
• Continuous Integration emerged in the Extreme
Programming (XP) community, and XP advocates
Martin Fowler and Kent Beck first wrote about
continuous integration circa 1999.

4
Continuous Integration
• 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

Ref: http://martinfowler.com/articles/continuousIntegration.html
5
Why Continuous Integration?
• Integration is hard, effort increase
exponentially with

– Number of components
– Number of bugs
– Time since last integration

Ref: http://www.slideshare.net/carlo.bonamico/continuous-integration-with-hudson 6
Continuous Integration Benefit
• Project Management
– Detect system development problems earlier
– Reduce risks of cost, schedule, and budget
• Code Quality
– Measurable and visible code quality
– Continuous automatic regression unit test

7
8
Best Practice of CI
• Single Source Repository.
• Automate the Build and Test
• Everyone Commits Every Day
• Keep the Build Fast
• Everyone can see what's happening
• Automate Deployment (Optional)

9
What’s Jenkins
1. An open source CI server
2. More then 85000 installations (May 2014)
3. Plug-in extensibility (Over 900 plugins)
4. MIT license

10
Continuous Integration Overview

Ref: http://www.javaworld.com/javaworld/jw-12-2008/images/CIOverview.jpg 11
Jenkins Features
• Trigger a build
• Get source code from repository
• Automatically build and test
• Generate report & notify
• Deploy
• Distributed build

12
Jenkins Requirement
• Web Server (Tomcat, WebLogic, …)
• Build tool (Maven, Ant)
• SCM (Git, Svn, Cvs, …)

13
Jenkins Plugins
• Build triggers
• Source code management
• Build tools
• Build notifiers
• Build reports
• Artifact uploaders
• UI plugins
• Authentication and user management
14
Build Trigger
• Manually click build button
• Build periodically
• Build whenever a SNAPSHOT
dependency is built
• Build after other projects are built
• Poll SCM
• IRC, Jabber, …
15
Get Source Code (1/2)
• CVS (build-in)
• SVN (build-in)
• GIT (requires Git)
• ClearCase (requires ClearCase)
• Mercurial, PVCS, VSS, …

16
Get Source Code (2/2)
• Get current snapshot
• Get baseline (tag)

17
Code Change History

18
Build Tools
• Java
– Maven (build-in), Ant, Gradle
• .Net
– MSBuild, PowerShell
• Shell script
– Python, Ruby, Groovy

19
Build Wrapper
• Build name (version no) setter
• Virtual machine (VMWare, Virtual Box)
• Set environment variable
• ClearCase release plugin
• …

20
Build Notifier
• E-mail
• Twitter
• Jabber
• IRC
• RSS
• Google calendar
• …
21
Build Report
• Static Code Analysis
– Checkstyle, PMD, Findbugs, Compiler
Warning
• Test Report & Code Coverage
– JUnit, TestNG, Cobertura, Clover
• Open Tasks

22
CheckStyle

23
FindBugs

24
Test Report

25
Test Code Coverage

26
Artifact uploaders
• Tomcat
• JBoss
• Glassfish
• WebSphere
• FTP
• SSH

27
UI Enhancement
• Dashboard
• Sectioned view
• iPhone/Android

28
Security Management
• Security Realm
– LDAP
– Jenkins's own user database
– Delegate to servlet container
• Authorization
– Anyone can do anything
– Logged-in users can do anything
– Matrix-based security
– Project-based Matrix Authorization Strategy
– Legacy mode
29
Security Management
• Matrix-based security

• Project-based Matrix Authorization

30
Security Management Plugins

• Active directory, OpenID, MySQL, …


• Role based privilege control

31
Plugin Usage Statistics

Ref: http://jenkins-ci.org/content/updated-usage-stats-available
32
Demo
Questions & Answers

34

You might also like