Concourse CI/CD

Concourse is built on the simple mechanics of

• Jobs
• Tasks
• Resources

Concourse presents a general approach to automation that makes it great for CI/CD.

Everything in Concourse runs in a container. Instead of modifying workers to install build tools, Tasks describe their own container image (typically using Docker images via the registry-image resource).

Prerequisites

Before getting started you should have the following installed:

• Docker
• Docker-compose

Before getting started you should have basic understanding of:

• What Linux containers are and how to work with them
• How to write Dockerfile
• YAML

Download Consourse Server and CLI

• Download concourse server v7.8.2
• Download concourse FLY CLI v7.8.2

Install Concourse

Through Docker compose

If you’d like to get Concourse running somewhere quickly the easiest way is to use councourse docker-compose.yml

Type http://localhost:8080/ in browser, you will see below page

Right click on login and open in new tab

default username : test and password: test.

After login page will be redirected to pipelines page to show all the set pipelines. In our case no pipeline is set yet.

Install Fly CLI

After the installation and running concourse you need to install Fly CLI to manage all the pipelines related operations.

Login to concourse local target instance

You can also login to remote concourse instance if you have URL and credentials available.But, definitely yes port 8080 must be opened in firewall to allow traffic from source.

Currently there is only 1 team main by default available.

• Pipelines are built around Resources, which represent all external state, and Jobs, which interact with them.
• Resources like the git resource and s3 resource are used to express source code, dependencies, deployments, and any other external state.
• Jobs are sequences of get, put, and task steps to execute. These steps determine the job's inputs and outputs.