In this slideshow I asked myself: Why should I prefer an on premise Jenkins vs SaaS like Travis? How can I set up Jenkins for multiple package versions (PHP 5.5, PHP5.4...) with an acceptable grade of maintainability?

1. JENKINS WITH
SUPER POWERS
Alessandro Mazzoli
am@ideato.it
@alendmazz

2. Why I should prefer on-premise
Jenkins
vs
SaaS like Travis or CircleCI ?

3. Let’s talk about $$$
TravisCI startup plan costs 130$/monthly
for 2 concurrent builds and several limits
c4.xlarge( 4 core, 8GB RAM,1Gb/s) ~ 130$/monthly
but I have to spend some time to configure
Jenkins…

4. Let’s talk about $$$
why should I keep my CI server always ON
even outside work hours??!!
here it comes on demand…
C4xlarge for 180h/720h ~ 32$

5. Let’s talk about $$$
but my sysadmin
has to switch on/off every day??!!
lot of waste and boring things!

6. Let’s talk about $$$
AWS CLI + CRON JOBS!!!
•20 9 * * 1-5 root/usr/local/bin/jenkins_on.sh
•50 19 * * 1-5 root /usr/local/bin/jenkins_off.sh
code will be available on https://www.ideato.it/blog

7. Let’s talk about heterogeneity
we have heterogeneous projects…
•PHP versions(5.4, 5.5,5.6)
•Elasticsearch(0.9->1.4)
•NodeJS
•….
with TravisCI I can easily set several PHP versions,
how can I run tests for these on JenkinsCI ?

8. Let’s talk about heterogeneity

9. Let’s talk about heterogeneity

10. Let’s talk about heterogeneity
docker images and reusability

11. Let’s talk about heterogeneity
docker images and reusability

12. Let’s talk about heterogeneity
docker images and reusability

13. a possible workflow…
All the additional software(ES, mongoDB..)
required should be defined in a Dockerfile,
committed inside the project repository
and built on top of CI image
Jenkins job will launch “composer install”,
build the image
and run tests inside the container

14. Our Dockerfile
for i.e we need Elasticsearch 1.4.2 & Node.js
run_tests will launch services inside the container

15. Our Dockerfile
run_tests will launch services
and tests through Idephix inside the container

16. Let’s talk about performance…
but you build the Dockerfile every time?
Not really…Docker use AUFS & caching
layers!!!

17. How do you manage the code??
git pull inside the container
or
shared code through DockerVolumes??

18. first approach more clean and isolate…
but Composer?
Composer for large project is a bottleneck
with our connectivity
on c4.xlarge we have 1Gb/s…

19. Let’s go on Jenkins

20. Resuming….
1 day for Jenkins setup
1/2 day for AWS cli cronjob
~ 550€
(one time cost)
+
AWS c4.xlarge 32€ x 12=384€ = 934€
vs
TravisCI Startup Plan 114€ x 12 = 1368€

21. Thanks for watching
Useful links:
http://getidephix.com/
https://www.ideato.it/blog