Continuous integration ( jen kins travis ci)

“ 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
2

Integration is hard , effort increase exponentially with
Number of components
Number of bugs
Time since last integration
4

 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
5

Immediate bug detection
 Reduce risk of cost schedule and budget
Measurable & visible code quality
Continuous automatic regression unit test
Record of evolution of the project
6

A hosted continuous integration service.
It is integrated with GitHub
9

Monitor GitHub projects
RunTests
Provide feedback
Build artefacts
Check code quality
Deploy to cloud services
Whatever you can make it do
10

Sign in toTravis CI with your GitHub account, accepting the
GitHub access permissions confirmation
 Once you’re signed in, andTravis CI synchronized your repositories
from GitHub, go to your profile page and enableTravis CI for the
repository you want to build.
12

 Add a .travis.yml file to your repository to tellTravis CI what
to build:
Travis CI tests this project against three versions of Ruby and
the latest version of Rubinius.
Add the .travis.yml file to git, commit and push, to trigger a
Travis CI build:
Check the build status page to see if your build passes or
fails.
13

Automatic integration with GitHub
First class support for 21 languages
Pre –installed build & test tools
Available services- databases , message queues
Encrypt secure environment variables or files
Clean environment
15

OS :Linux ,mac
Anroid
C++
C
C#
Java
Php
Perl
Python
Visual basic
Java script
Go
Groovy
16

Easy to configure & use
High speed
It’s popular
Great integration with GitHub & cloud services
17

No manual builds
No build pipelines
Not suitable for high security projects
Less extensible than JenKins
18

Branched from Hudson
Java based Continuous Build System
 Runs in servlet container
Glassfish,Tomcat
Supported by over 400 plugins
Under development since 2005
http://jenkins-ci.org/
20

2005 - Hudson was first release by Kohsuke Kawaguchi of
Sun Microsystems
 2010 – Oracle bought Sun Microsystems
Due to a naming dispute, Hudson was renamed to Jenkins
 Oracle continued development of Hudson (as a branch of
the original)
Jenkins - History
21

Easy installation
Easy configuration
Rich plug in ecosystem
Extensibility
Distributed builds
Flexibility
22

Use one of the platform-specific package/installer links on the Jenkins
site to install Jenkins on your system
You can download jenkins.war directly and launch it by executing java -
jar jenkins.war.This is basically the same set up as the test drive, except
that the output will go to console, not to a window.On Windows, you
can even choose to install Jenkins as a service afterwards
License
Jenkins is distributed under the MIT License
23

Web server(Tomcat , WebLogic)
Build tool (Maven, Ant)
SCM(Git, Svn , Cvs)
24

 Build triggers
 Source code management
 Build tools
 Build wrappers
 Build notifiers
 Build reports
 Authentication and user management
25

 Generate test reports
 Integrate with many differentVersion Control Systems
 Push to various artefact repositories
 Deploys directly to production or test environments
 Notify stakeholders of build status
26

When setting up a project in Jenkins, out of the box you have the
following general options:
 Associating with a version control server
 Triggering builds
 Polling, Periodic, Building based on other projects
 Execution of shell scripts, bash scripts, Ant targets, and Maven
targets
 Artefact archival
 Publish JUnit test results and Javadocs
 Email notifications
 Plugins expand the functionality even
further
27

 Once a project is successfully created in Jenkins, all future builds
are automatic
 Building
*Jenkins executes the build in an executer
*Jenkins also has the concept of slave build servers
. Useful for building on different architectures
. Distribution of load
28

Jenkins comes with basic reporting features
Keeping track of build status
 Last success and failure
 “Weather” – Build trend
These can be greatly enhanced with the use of pre-build plugins
 Unit test coverage
Test result trending
 Findbugs, Checkstyle, PMD
29

TRAVIS CI
 Commercial
 Service
 Convention
 Easy to use
JENKINS
 Open-Source
 Application
 Configuration
 Flexible
31

http://www.uqasar.eu/review-saas-continuous-integration-tools-series/
Continuous Integration (Jenkins/Hudson) - SlideShare
[PPT]CI-201110.ppt
[PDF]Jenkins Continuous Build System
http://www.slideshare.net/bsiggelkow/travis-ci
http://www.slideshare.net/gabevanslv/travis-ci-23997525?related=1
https://docs.travis-ci.com/user/getting-started/
32

Continuous integration ( jen kins travis ci)

More Related Content

What's hot (20)

Similar to Continuous integration ( jen kins travis ci) (20)

Recently uploaded (20)

Continuous integration ( jen kins travis ci)