Learn CONCOURSE-CI with Real Code Examples

Install Concourse server (ATC) and worker nodes

Set up PostgreSQL or other backend for state persistence

Configure authentication (optional: GitHub, LDAP, or local users)

Install `fly` CLI for pipeline management

Verify setup by logging into web UI and running test pipelines

Install Concourse ATC and workers

Configure database backend (PostgreSQL)

Set up authentication (optional)

Install fly CLI for pipeline management

Test pipelines via web UI and CLI

pipeline.yml - main declarative pipeline

tasks/ - reusable task scripts

resources/ - optional external definitions

credentials.yml - secret integration

README.md - documentation

fly set-pipeline

fly unpause-pipeline

fly pause-pipeline

fly execute

fly watch

YAML files support UTF-8

Logs can include multi-language output

Resource naming flexible for localization

UI text may vary by browser locale

External scripts support any language

Accessible via web browser

CLI access with fly

REST API for integration

Visual pipeline status for teams

Multi-user role management

Web UI for pipeline visualization

Real-time job status and logs

No advanced graphical styling

CLI provides alternative interaction

Third-party dashboards possible via API

Pipeline versions tracked via YAML

Artifacts and outputs persist between tasks

Secrets managed externally

Job statuses and history tracked by ATC

Resource versions ensure reproducible builds

Task outputs stored as artifacts

Resource versions tracked

Logs captured for each task

Secrets kept in Vault or credential manager

Pipeline outputs can feed downstream jobs