CloudShell Colony blueprint repository for Jenkins deployment

This blueprint repository allows you to easily deploy Jenkins and connect it to your Cloudshell Colony account. After deployment this Jenkins instance could be immediately used to launch your pipelines against environments provided by Colony. It comes with a sample 'demo' pipeline, so that you will have an entrypoint from where you can start modeling your CI/CD flows using Jenkins and Colony

Repo consists of two blueprints:

Jenkins

This blueprint deploys a Sandbox with Jenkins itself. Flow is the following:

• It first deploys jenkins
• Installs colony jenkins plugin and it's dependencies
• Configures connection between Colony and Jenkins
• Creates a sample demo pipeline

Promotions Manager

It's a demo blueprint which is used by the pre-defined pipeline in Jenkins. It deploys a sandbox with sample app consisting of backend, frontend and database.

How To Use

prerequisites:

• Only AWS cloud provider is currently supported
• Before starting using this solution you need to have an S3 bucket created to store artifacts built by the sample Jenkins job
• You also need to create an IAM role (for EC2 service) and configure it with write permissions to your S3 bucket

Colony setup

Link you AWS account and S3 bucket to Colony

Go to Settings and link your aws account on Cloud Account page and set your s3 bucket as an artifacts repository on Integrations page

Connect blueprint repo to your Colony space

In your space go to Settings -> Blueprint Repositories and connect this repo as a blueprint repository for Sandbox Environment. If you want to do some experiments with code and make some changes fork it and connect your own repository

Activate blueprints

Go to Blueprints and publish both Jenkins and Promotions Manager blueprints in "Space Blueprints" list

Now you can start working with the Jenkins blueprint

Jenkins Blueprint Usage

Now you are ready to launch a sandbox with Jenkins on Sandbox Environment page

Jenkins Blueprint has the following list of input parameters:

AWS_INSTANCE_TYPE - specify the type of aws instance according to required size (default is m5.large)

JENKINS_ADMIN_PASS - set the password which you will use when logging in to Jenkins with admin user. Default is "admin"

CS_COLONY_TOKEN - token which Jenkins will use to communicate with Colony. You can generate it on Settings -> Integrations page

IAM_ROLE - IAM role instance profile name you've created at the beginning

SPACE_NAME - the name of the space which Jenkins will use to run sandboxes from. For our example just specify the name of your current space. Note: In future you might want to create your personal blueprints and configure Jenkins pipelines to use them. These blueprints will probably live in other spaces.

BUCKET_NAME - name of S3 bucket connected to the space you created for artifacts

Demo pipeline

After sandbox deployment you can log into Jenkins by using quick link:

In Jenkins you will see a pre-defined pipeline which is configured to run a Promotions manager blueprint in your Colony space

Pipeline steps

The default pipeline loaded with this Jenkins instance will automatically run the following steps:​

1. Retrieve latest code of the promotion app from Git​
2. Build artifact package (latest build)​
3. Upload Build to S3 repository​
4. Deploy the promotions manager application to AWS in a Colony Sandbox​
5. Run tests​
6. Terminate the promotions manager application