CI

Continuous IntegrationStop procrastinating and build often!

Who am I?Patrick MizerChief Architect at SpareFootZCE: PHP4, PHP5, and ZF

[email protected]/maximizer

mailto:[email protected]

mailto:[email protected]

We help consumers search, compare, and book self storage online.

I’m not supposed to say this but… Think Hotels.com, but for self storage.

We have been using a Continuous Integration workflow since 2009

SpareFoot in 2009❏ 20 Visits per day❏ 1 RackSpace cloud instance❏ 2 Developers❏ 1 Application❏ 5-10 builds per day❏ Deployed whenever -> % svn up

SpareFoot Today❏ 2 million visitors per month❏ > 50 AWS EC2 instances❏ 35 developers ❏ 7 product teams.❏ 100-200 builds per day❏ Continuous Delivery

What I will cover...❏ What is CI?❏ Why do it?❏ The Jenkins CI Server❏ What does a CI workflow look like?❏ Build Tools❏ Testing and Analysis❏ Notification❏ Lessons Learned

I want to clarify something..

Continuous something...

Continuous Integration

Continuous Delivery

Continuous Deployment


ContinuousIntegration

ContinuousDelivery

ContinuousDeployment


Version Control

Deploy to Staging

AutomatedTests

AUTO AUTO


ContinuousDelivery



Version Control

Deploy to Staging

AutomatedTests

Acceptance Tests

Deploy to Production

AUTO AUTO AUTO MANUAL

Version Control

Deploy to Staging

AutomatedTests

AUTO AUTO


ContinuousDelivery



Version Control

Deploy to Staging

AutomatedTests

Acceptance Tests


AUTO AUTO AUTO AUTO

Version Control

Deploy to Staging

AutomatedTests

Acceptance Tests


AUTO AUTO AUTO MANUAL

Version Control

Deploy to Staging

AutomatedTests

AUTO AUTO


ContinuousDelivery


What is Continuous Integration?

CI is a software development process in which developers integrate their work frequently.

Each integration is built and verified by automated tests so that errors and inconsistencies are detected and fixed as quickly as possible.

What is Continuous Integration?

CI originated with Extreme Programming

CI is a process. It dictates no specific tooling.

So, why do it?

Finding bugs late is costly

Local

Development

Staging

Production

Developers

QA & Stakeholders

Your Customers

Finding bugs late is costly

Integration Hell

“Your changes to the booking service are incompatible with mine. How do we merge now?”

“When did we start using Guzzle 2.0? The SDK requires 3.0 and composer won’t let us use both!”

Integration Hell

Mainline

Developer C

Developer A

Developer B

Poor Quality Codebase

“Who the #$@# is using tabs instead of spaces!?”

“We have 2 classes doing the exact same thing”

Poor Project Visibility

“What is our test coverage?”

“How is our app performing?”

No Deployable Code

“It works on my machine!”

“I don’t know why it’s not working on staging, sounds like an ops problem.”

“We need to push a fix for this immediately.”

CI attempts to mitigate these

❏ Finding bugs late is costly❏ Integration hell❏ Poor quality code base❏ Poor project visibility❏ No deployable code

Better code, faster development

Better code❏ Code is tested early and often❏ Standards enforced on every commit

Better code, faster development

Better code❏ Code is tested early and often❏ Standards enforced on every commit

Faster development❏ Integration issues are found earlier❏ Testing becomes part of everyone’s process❏ Building is a non-event


Implementing a CI solution is pretty straightforward.


❏ Maintain an SCM code repository


❏ Maintain an SCM code repository❏ Create and automate the build


❏ Maintain an SCM code repository❏ Create and automate the build ❏ Everyone commits to mainline (at least daily)


❏ Maintain an SCM code repository❏ Create and automate the build ❏ Everyone commits to mainline (at least daily)❏ Every commit to mainline is built


❏ Maintain an SCM code repository❏ Create and automate the build ❏ Everyone commits to mainline (at least daily)❏ Every commit to mainline is built❏ Tests verified on a prod-like environment


❏ Maintain an SCM code repository❏ Create and automate the build ❏ Everyone commits to mainline (at least daily)❏ Every commit to mainline is built❏ Tests verified on a prod-like environment ❏ Notify everyone of the results

Excuses“We're not big enough”

“Too much work”

“We don't have devops”

“We don't have tests”

The CI Server❏ Polls for changes❏ Manages and monitors builds❏ Notifies team of results

Jenkins❏ Free Open Source (MIT License)❏ Built on Java❏ Fork of Hudson❏ Plugins for everything❏ Lots of resources

Easy to get going:% sudo apt-get install jenkins

% sudo apt-get install jenkins-cli

Jenkins-php.orgJenkins template for PHP projects put together by Sebastian (yes, that Sebastian) Bergmann

Step-by-step Instructions:❏ Template w/ plugins❏ Build file❏ Log formats❏ Jenkins config

The CI workflow❏ Developer commits code❏ CI Server polls SCM for changes❏ CI Server integrates and builds code

to the Integration Environment❏ CI notifies team of result

The CI workflowPush

The CI workflow

Poll

Push

The CI workflow

Poll

Build

Push

The CI workflow

Poll

BuildTest/Analyze

Push

The CI workflow

Poll

BuildTest/Analyze

Notify

Push

The Build❏ Build dependencies❏ Tests❏ Static analysis❏ Artifacts (docs, phar, etc)❏ ...

Build tools...

Build tools...“But build files are only for compiling.”

Build tools...Use a proper built tool❏ Apache Ant (Java) ❏ Phing (PHP)

Apache Ant❏ build.xml❏ Targets and depends❏ Java = threads ++

Anatomy of build.xml<?xml version="1.0" encoding="UTF-8"?>

<project name="some-php-project" default="build">

<target name="build" depends="phpunit"/>

<target name="phpunit" description="Run unit tests">

<exec executable="phpunit" failonerror="true"/>

</target>

</project>

SCM polling and build

The Integration Machine❏ A reasonable facsimile of production❏ Every commit is built here❏ By yourself? Use Vagrant

Verifying the BuildUnit Tests Functional Tests

Selenium “But setting up selenium is hard...”

SauceLabs

Testing is just the beginning

Static Analysis

Analysis of software without actually executing the code.

Check your PHP syntax

PHP Lint

php -l foo.php

find . -name “*.php” -exec php -l {}\;

PHP Lint

Coding Standards

PHP Code Sniffer

phpcs --standard=pear foo.php

PHP Code Sniffer

DRYCopy page detector

phpcpd -min-lines=5 /src/service/*

Copy Paste Detector

Performance

Performance - BonusPhantomjs is a headless browser based on Webkit with JS API

YSlow is a tool that analyzes web pages and why they’re slow based on Yahoo’s rules.

Phantomjs + YSlow = Awesomeness

Performance - Bonusphantomjs yslow.js -i grade -threshold "A" -f junit http://staging.sparefoot.com > results.xml

Notification

Lessons Learned

Lessons LearnedVersion all of you CI Config.

We didn’t and now we’re going back and rewriting it.

Lessons LearnedBuilding the DB❏ Put your schema changes under version

control.❏ Incorporate them into the build❏ Fail when there’s a problem. Make this the

only way to get schema changes to production.

Git feature branchingGit feature branching solves a separate problem.

Git feature branching

Master

Branch C

Branch A

Branch B

Our Git Workflow

commit commit PUSH

Branch

Merge

Pull request

commit

PUSHcommit commit commit

Merge

Pull request

MASTER

BRANCH B

BRANCH A

Branch + master built to dev environment and tested.

Branch + master built to dev environment and tested.

Master built to staging environment and tested.

Play with Jenkins today!github.com/maximizer/vagrant-ci% git clone github.com/maximizer/vagrant-ci.git

% vagrant up

http://localhost:8282

http://jenkins-php.org





Thank You!

Questions?

https://joind.in/[email protected]/maximizer/vagrant-ci

CI

Documents

Transcript of CI