Continous Delivering a PHP application

APPLICATIONS

CONTINUOUSLY!DELIVERING

Javier López @loalf

Senior Platform Engineer @Rightster!formerly Software Architect @TimeOut

Certified Symfony Developer

Zend Certified PHP

Co-organizer @desymfony

DISCLAIMER

AGENDA

CONTINUOUS DELIVERY IN A NUTSHELL

BUILDING THE PIPELINE

BEFORE AND AFTER

1

2

3

CONTINUOUS DELIVERY …

… IN A NUTSHELL

1

COMMIT BUILD TEST DEPLOY

When and how a change in your code is going to trigger the pipeline


Check the integrity of your code. Produce an artifact.


Check the integrity of your product. !

After this step you should be 100% confident that you could deploy your artifact.


Does what it says on the tin. Triggering this step should be “a click away”.

Manual

THE BOOK

THE PIPELINEBUILDING

2

TOOLS!OF THE TRADE

Github pluginhttps://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin

Build Pipeline Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin

https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin

https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin

BUILDING!THE PIPELINE


master

6ebb017


master

featureA

6ebb017


master

featureA

6ebb017

PULL REQUEST


master

featureA

6ebb017 9046c48


master

featureA

6ebb017 9046c48

BUILD TEST DEPLOY


1. Check out master branch


1. Check out master branch2. Generate parameters.ini for each environment



3. Fetch PHP dependencies





—optimizer-‐autoload —prefer-‐dist





3. Fetch PHP dependencies4. Run PHPUnit tests



3. Fetch PHP dependencies4. Run PHPUnit tests5. Fetch JS dependencies



3. Fetch PHP dependencies4. Run PHPUnit tests5. Fetch JS dependencies6. Generate assets (JS, CSS)



3. Fetch PHP dependencies4. Run PHPUnit tests5. Fetch JS dependencies6. Generate assets (JS, CSS)7. Generate artifact (zip file)





discard unnecessary files





3. Fetch PHP dependencies4. Run PHPUnit tests5. Fetch JS dependencies6. Generate assets (JS, CSS)7. Generate artifact (zip file)8. Upload artifact to S3



3. Fetch PHP dependencies4. Run PHPUnit tests5. Fetch JS dependencies6. Generate assets (JS, CSS)7. Generate artifact (zip file)8. Upload artifact to S3

COMMIT BUILD TEST DEPLOYbuild.xml

<?xml version="1.0" encoding="UTF-‐8" ?> <project name="Time Out Miyagi" description="Time Out Website V4" default="build" ! <!-‐-‐ Install PHP dependencies (composer) -‐-‐> <target name="build:php-‐dependencies" depends="build:params"> <echo msg="Installing PHP dependencies (composer install)" /> <exec command="/opt/composer/composer.phar install -‐-‐optimize-‐autoloader -‐-‐prefer-‐dist" logoutput="true" checkreturn=“true" /> </target> ! <!-‐-‐ Test JS & Generate JS/CSS assets (grunt) -‐-‐> <target name="build:frontend-‐dependencies"> <echo msg="Test JS and Generate JS/CSS assets (grunt)" /> <exec command="npm install" logoutput="true" checkreturn="true" dir="./web-‐src" /> <exec command="xvfb-‐run grunt -‐-‐env=dist" logoutput="true" checkreturn="true" dir="./web-‐src" /> </target> </project>

build.xml


Split into two jobs in Jenkins 1. Test deployment script 2. Run automated tests


DEPLOYMENT SCRIPT


DEPLOYMENT SCRIPT

1. SSH to QA server


DEPLOYMENT SCRIPT

1. SSH to QA server2. Fetch artifact from S3


DEPLOYMENT SCRIPT

1. SSH to QA server2. Fetch artifact from S33. Unzip artifact


DEPLOYMENT SCRIPT

1. SSH to QA server2. Fetch artifact from S33. Unzip artifact4. Set right permissions


DEPLOYMENT SCRIPT

1. SSH to QA server2. Fetch artifact from S33. Unzip artifact4. Set right permissions5. Update virtual host


DEPLOYMENT SCRIPT

1. SSH to QA server2. Fetch artifact from S33. Unzip artifact4. Set right permissions5. Update virtual host6. Reload PHP-FPM and nginx


DEPLOYMENT SCRIPT

1. SSH to QA server2. Fetch artifact from S33. Unzip artifact4. Set right permissions5. Update virtual host6. Reload PHP-FPM and nginxdeploy.yml

-‐-‐-‐ -‐ hosts: qa:beta:prod sudo: true vars: amazon_bucket : "releases-‐miyagi" base_dir : "/var/www/v4.timeout.com" project_dir : "{{ base_dir }}/{{ git_hash }}" web_dir : "{{ project_dir }}/web" tasks: -‐ name: Fetch artefact from S3 s3: bucket={{ amazon_bucket }} aws_access_key={{ amazon_key }} aws_secret_key={{ amazon_secret }} object={{ git_hash }}.gzip dest="{{ project_dir }}/{{artefact_zip}}" mode="get" ! -‐ name: Uncompress zip file command: chdir="{{ project_dir }}" tar -‐xf {{ artefact_zip }} ! -‐ name: Apply right permissions to project root file: dest="{{ project_dir }}" state=directory mode=0755 group=nginx owner=nginx recurse=true -‐ name: Restart PHP-‐FPM service: name=php-‐fpm state=reloaded

deploy.yml


RUN AUTOMATED TESTS


RUN AUTOMATED TESTS

1. Check out 9046c48


RUN AUTOMATED TESTS




RUN AUTOMATED TESTS


2. Fetch PHP dependencies3. Run Behat against QA box


Split into two jobs in Jenkins 1. Run deployment script (production) 2. Run automated tests against production

BUILD DEPLOY AUTOMATED!TESTS

6ebb017

6ebb017

QA

6ebb017

QA

DEPLOY AUTOMATED!TESTS

6ebb017

PROD

6ebb017

PROD

6ebb017

6ebb017.zip


6ebb017

6ebb017

QA

6ebb017

QA


6ebb017

STAGING

6ebb017

STAGING


6ebb017

PROD

6ebb017

PROD

6ebb017

6ebb017.zip

SAFETY NET

TIME


~3 mins ~30 secs ~5 mins

VISIBILITYEVERYBODY IN THE TEAM SHOULD BE

AWARE OF THE STATUS OF THE PIPELINE


9046c48

9046c48

QA

9046c48

QA9046c48


6ebb017

6ebb017

QA

6ebb017

QA6ebb017


b0b325

b0b325

QA

b0b325

QAb0b325


99e6d6

99e6d6

QA

99e6d6

QA99e6d6

http://www.frisnit.com/internet-of-things-ci-status-lamp/

TRACEABILITYEVERYBODY SHOULD KNOW WHAT VERSION

IS DEPLOYED IN WHICH ENVIRONMENT

curl -‐I http://www.timeout.com/las-‐vegas !HTTP/1.1 200 OK Server: nginx/1.4.7 Vary: Accept-‐Encoding Cache-‐Control: no-‐cache Content-‐Type: text/html; charset=UTF-‐8 Date: Fri, 19 Sep 2014 06:07:29 GMT Transfer-‐Encoding: chunked Access-‐Control-‐Allow-‐Origin: http://media.timeout.com Connection: Keep-‐Alive X-‐TIMEOUT-‐V: d645127afb423e543d90ab5a7b8eae94f248b137 X-‐Powered-‐By: PHP/5.5.14

VERSION NUMBER

http://www.timeout.com/las-vegas

https://github.com /your-‐company /your-‐application /commits /your-‐git-‐hash

https://github.com

ROLLING!BACK

AUTOMATION

YOU’LL NEED!ALLIES

YOUR ALLIES

DEV TEAM

YOUR ALLIES

DEV TEAMQA TEAM

YOUR ALLIES

DEV TEAMQA TEAMDEVOPS

YOUR ALLIES

DEV TEAMQA TEAMDEVOPSPRODUCT

YOUR ALLIES

DEV TEAMQA TEAMDEVOPSPRODUCTTHE TOP BRASS

YOUR ALLIES

BEFORE AFTER &

3

ONE QA BOX PER FEATURE

SAME QA BOX FOR EVERYONE

BEFORE

AFTER

~ !WEEKS FROM DEVELOPMENT TO RELEASE

~ !DAYS FROM DEVELOPMENT TO RELEASE

BEFORE

AFTER

5 PEOPLE TO RELEASE TO PRODUCTION

1 PERSON TO RELEASE TO PRODUCTION

BEFORE

AFTER

~30 MINUTES TO RUN DEPLOYMENT SCRIPT

~30 SECONDS TO RUN DEPLOYMENT SCRIPT

BEFORE

AFTER

RELEASING WAS AN EVENT

RELEASING NOW A NON-EVENT

BEFORE

AFTER

@loalf

Technology

Continous Delivering a PHP application