Sunbird Deployment Pipeline Overview

Purpose

This document explains the Sunbird Deployment Pipeline, the tools and standards used to create the pipeline. The standards make is simple to discover the existing pipelines and also to setup pipelines for new services.

Tools used

Following open-source tools/frameworks have been used

• Jenkins
• Ansible
• Docker Hub (Image Registry)

Deployment Pipeline Architecture

Link

• Sunbird has two deployment environments, dev and staging.
• Single Jenkins Master is used for both the environments.
• Each environment has Jenkins agent service (jenkins agent which runs as a docker container) which is used by the Master to run jobs. Dockerfile for building this image is here
• Depending on the number of jobs being executed Jenkins agent service could be either scaled up or down.
• There is also a Jenkins Build Agent which runs natively (not a docker container) on a VM in dev environment. This could be used for running jobs which cannot be run on Jenkins agent service (docker container). Note: As a best practice we recommend that jobs be run on the container agent, so that scaling becomes easy, if required. Running the job on a VM agent is discouraged and should be treated as a short term solution.