1. Continous delivery pipeline
for Symfony2 projects with
Jenkins and Chef
Michał Dąbrowski
http://github.com/defrag
PHPers Kraków 10/07/2014

3. Most common anwser?

4. Most common anwser?
Should be done

5. Most common anwser?
Should be done

6. „Continuous delivery (CD) is a set of
processes, tools and techniques for the
rapid, reliable and continuous
development and delivery of software.”
What is continous
delivery?

7. Our highest priority is to satisfy the
customer!
through early and continuous delivery!
of valuable software.
Agile manifesto #1

8. done === released
What is done in
Continous Delivery?

9. Why?
increase quality
reduce cost
reduct risk
make customer happy
delivery production ready software
act on feedback

10. Quality comes first

11. Building blocks from
practical view
Continous Integration
Release automation
Infrastructure automation
Monitoring

12. CI & Deployment
pipeline

13. Typical development
workflow
Fork a repo

14. Typical development
workflow
Submit pull request

15. Typical development
workflow
Trigger build process on PR

16. Typical development
workflow
Code review

17. Typical development
workflow
Merge into master

18. Typical development
workflow
Trigger build on master branch

19. Typical development
workflow
Result of build is Release Candidate!
(not every RC is deployed)

20. How do we get
there?

21. Start with Jenkins

22. Create new project

23. Set up your build
process

24. Set up your build
process
<target name="configure">
<echo>Downloading dependencies using composer.</echo>
<exec executable="/bin/bash" failonerror="true" dir=„.">
<arg value="/usr/bin/composer install —no-interaction —prefer-dist" />!
</exec>
!
<echo>Dumping prod assets.</echo>
<exec executable="/bin/bash" failonerror="true">
<arg value="-c" />
<arg value="${basedir}/bin/console assetic:dump --env=prod --no-debug" />!
</exec>
!
<echo>Ensuring empty cache and logs directories.</echo>
<delete includeemptydirs="true" verbose="false" failonerror="true" dir="${basedir}/var/cache" />!
<delete includeemptydirs="true" verbose="false" failonerror="true" dir="${basedir}/var/logs" />!
<mkdir dir="${basedir}/var/cache" />!
<mkdir dir="${basedir}/var/logs" />
</target>

25. Run your unit tests

26. Run your unit tests
<target name=„phpspec" description="Run tests with PHPSpec">
<exec executable="/bin/bash" failonerror="true">
<arg value="-c" />
<arg value="${basedir}/bin/phpspec run" />
</exec>
</target>
<target name="build-unit">
<property file="build.ci.properties" />
<antcall target="phpspec" /> !
<antcall target="jasmine" />
<echo>Unit test build pass.</echo>
</target>

27. Run your acceptance
tests

28. Run your acceptance
tests
<target name=„behat" description=„Run acceptance tests with Behat">
<exec executable="/bin/bash" failonerror="true">
<arg value="-c" />
<arg value="${basedir}/bin/behat —format progress" />!
</exec>
</target>
<target name="build-acceptance">
<property file="build.ci.properties" />
<antcall target="behat" /> !
<echo>Acceptance test build pass.</echo>
</target>

29. Create package out
of build result
• tarball!
• rpm!
• deb!
• etc.

30. Create package out
of build result

31. Visualize your process
with build pipeline

32. Stop
Deploy time

33. Not only application
Deliver your configuration in automated fashion

34. Build pipeline
revisited
manualauto

35. Quick Chef overview

36. Make jenkins talk to
your chef server
knife ec2 server create!
knife bootstrap!
knife ssh!
…

37. Make jenkins talk to
your chef server

38. Deploy app
capistrano, fabric, knife plugin etc

39. Chose the one that
works for you

40. Dead simple with
Fabric and pychef
@roles('web')!
def deploy():
…

41. Dead simple with
Fabric and pychef
fab env:staging deploy:25

42. Dead simple with
Fabric and pychef
fab env:staging deploy:25
chef environment build no.

43. Demo

44. Wrapping up

45. Benefits
speed of delivery
quality
cost reduction
ability to respond to feedback quickly
adapt to change

46. Thank you