This document summarizes Noam Shochat's presentation at the Jenkins User Conference Israel on building a deployment pipeline at eToro. It describes eToro's infrastructure with 120 services, 300 servers across 3 data centers and 2 clouds. It outlines the problems they faced with manual deployments and lack of uniformity. The solution involved using Jenkins for continuous integration and delivery, along with Mcollective for orchestration and Puppet for deployment automation. Key components of the pipeline included committing code, building, running unit tests, deploying to QA, running integration tests, and deploying to production.

1. Jenkins User Conference Israel #jenkinsconf
Building a deployment
Noam Shochat
@noamshochat
eToro
www.etoro.com
July 16, 2014
pipeline
#jenkinsconf

2. Amount of
Work
Time
Current
Reality
What we think
will happen
Adding automation

3. A little bit about eToro
● 120 Services
● 300 Servers
● 3 Data centers
● 2 Clouds
● .Net
●

4. The problem
● Builds
● Manual deployments
● Lack of uniformity
● Different OS’s
● Slowness
● Different Environments
● Security
Developer Production

5. The Solution
Code commit
CI / CD
Production Build, Unit tests
Deploy and tests in QA

6. We choose Jenkins
BUT…
Not good for:
● Deployment
● Orchestration

7. So we also choose to use:
● Mcollective + Ruby for orchestration
● Puppet for deployment (and more)
● RabbitMQ for connecting between them

8. Pipeline
Commit
Build Unit tests Trigger
ruby
Developer
QA - Jenkins
Servers
Puppet
Puppet
Puppet
Integration
tests
Production - Jenkins
Servers
Puppet
Puppet
Puppet
Trigger
MCollective
Trigger
MCollective
Trigger
ruby

9. In Jenkins

10. Flow

11. Flow
out.println 'Starting OpenBookSearchAPI Flow'
b=build("OpenBookSearchAPI-Build")
parallel(
{
build("OpenbookSearchAPIBack-iis")
},
{
build("OpenbookSearchAPI-Service-Stop")
build("OpenbookSearchAPI-Service")
build("OpenbookSearchAPI-Service-Start")
}
)

12. Build

13. Build
● Mercurial
● Build start by trigger
● MSBuild
● NUnit tests + dot cover

14. Deployment

15. Deployment
● Use Ruby for trigger and orchestrate using
MCollective
● Puppet do the deployment

16. Integration tests

17. Integration tests
● Canary tests

18. Health check

19. Health check
● What is it?
● Json file that checks dependencies and
basic sanity test

20. Publish

21. Publish
● Almost in production
● Build version file as the gatekeeper to
production

22. Production deploy
● Build version file
● rsync

23. CloudShare
● Jenkins CLI
● Dynamic jenkins agents
● The flow continue the same changes to
same flow

24. Plugins we’re using
● MSBuild
● HTML Publisher
● Nested View
● Build Flow
● Active directory
● statsd

25. Our CI/CD servers
Jenkins
master
+ MCollective RabbitMQ WebApp
Servers
Puppet
master
Ruby
script

26. Q&A

27. Jenkins User Conference Israel #jenkinsconf
Thank You To Our Sponsors
Platinum
Gold
Silver