Quick Start Guide

Purpose

This guide will give you an understanding of the elements that needs to be updated in order get up and running with the Jenkins environment provision by the ansible scripts.

The Jenkins environment that is provided by the ansible script is configured for general usage. What this mean is that, there isn't a “one configuration fits all scenario”. The continuous integration environment has to be configure on a case by case basis. In order to accomplish this, you’re required to have some familiarity with the following elements before proceeding:

• Docker
• Jenkins (of course)
• CoreOS (this is optional since deployment can happen on other environments that support containers.)

There is a wealth of documentation here. Its highly recommended that you review this document.

Below there are links pointing to specific elements that can help as well.

Each step is listed below with the required items identified.

All the Job in the pipeline may require important build variables to be propagated throughout the pipeline an example of this can be found here

GetLatestFromSCM

• SCM url
• Build variables e.g. APP_VERSION_TAG this will be used for tagging the docker containers when they’re push to the docker hub.

IntegrationTesting

• Configure Docker slave - link to documentation

UnitTesting

• Configure Docker slave - link to documentation

PushToDockerHub

• Configure the Jenkins build and push plugin with the appropriate credentials. Documentation can be found here.

FunctionalTesting

• Configure Docker slave - link to documentation
• Configure to use the appropriate tools to run functional tests e.g. Sauce labs.

PushToDockerHub-QA

• Configure the jenkins build and push plugin with the appropriate credentials.Documentation can be found here.

DeployToQA

• Configure Docker slave - link to documentation
• This can be any remote environment that supports container deployment e.g. CoreOS.

Sample Build Variables

These are some sample build variables that can be used in your build pipeline, to make the pipeline configurations cleaner.

This can be used with parameterized-trigger that already provision on Jenkins, once this script was used to provision it. Documentation on this plugin can be found here.

DB_NAME - Test database name
CI_DB_DOMAIN - Address for the CI test database
CI_DB_PORT - Port for the CI test database
QA_DB_URL - Address for the QA test database
QA_DB_PORT - Port for the CI test database
APP_VERSION_TAG - Unique tag for the docker container
APP_SERVER - Address for the application server
FLEETCTL_TUNNEL - IP address for the CoreOS fleet
CI_HTTP_PORT - IP address per build when doing functional test