This document discusses continuous delivery (CD) pipelines and how InstallCore uses CD. It describes a classic CD pipeline with development, build, test, and deployment stages. For InstallCore, testing occurs through unit tests, integration tests on a QA environment, and performance/regression tests on a staging environment. The document also explains how InstallCore scales CD by integrating JIRA for ticket management and control, using Robot Framework for automated testing, migrating from Bamboo to Jenkins for scalability, and moving from VMware to Ravello on AWS to enable parallel testing environments.

1. Continuous Delivery
InstallCore, IronSource
August 2015

2. Classic CD Pipeline
DEV BUILD TEST DEPLOY
Product
Customer

3. Testing in CD
TEST
Unit test
and static
code
analysis
deploy to
QA env
integration
test on QA
env
deploy to
Staging
env
Regression
test on
Staging
env
Perf, load
.. test on
Staging
env

4. InstallCore Use Case
DEV BUILD TEST DEPLOY
5 builds / month
> 500 builds / month50 builds / month
Control & Scalability

5. Control - JIRA integration
● Automatic transition from state to state using
groovy script in JIRA workflow (jython)
● Control on the releases
● Auto assign to the relevant people / department
in case of failure
● Alert in case of irregular queue or ticket that not
released in time
setup job ( branch / template..)
build job
test job
release job

6. JIRA - Robot Framework
ticket fields are used as test data for the robot test
● business account manager fill the requirements in the ticket
● os / browser supported (use of robot tag)
● specific data tested (use of include / exclude)
test_params.pyexecution_params.json

7. Scalability -
from Bamboo to Jenkins
Robot framework jenkins plugin
Test Report integrated to build results
no licence
no build agent limitation

8. Scalability -
from vmware to AWS via Ravello
Test faster with any number of automated parallel environments
windows 10 use case

9. Thank you
Ariel Levy
ariel@ironsrc.com
054 - 4641230