What is Pivotal Concourse?
Concourse is a continuous integration tool that lets you build, scale, and monitor pipelines outside of your Pivotal Platform deployment. Using Concourse, you can set up production pipelines to deploy and manage your apps in real time. Pivotal Concourse is an officially supported, long-term-stable version distributed through Pivotal Network.
Installing Pivotal Concourse
Pivotal Concourse is distributed as both a BOSH release and a Helm Chart.
The BOSH release requires the operator to install and maintain an independent BOSH Director.
If you are unfamiliar with BOSH, Pivotal recommends that you review the BOSH documentation before continuing with the installation of Pivotal Concourse.
Use the BOSH CLI v2 or v3 with Pivotal Concourse. Pivotal does not recommend using the old BOSH CLI v1 with Pivotal Concourse.
Concourse now also supports a Helm Chart release. Where the BOSH release targets a BOSH director and deploys to virtual machines (VMs), the Helm Chart release instead targets Kubernetes clusters using the templating and release management of Helm.
When you are ready to get started with either release, see the step-by-step guide to Installing Pivotal Concourse for more information.
Additional Enterprise Considerations
Concourse lets you encrypt sensitive information before it reaches the database. By using encryption, you ensure that plaintext credentials do not exist in memory for longer than absolutely necessary.
For more information, see Encrypting Concourse Databases.
With Concourse credential management, pipeline credentials can be parameterized with ((parameters)) in your pipeline or task config files.
Credential management also allows for credentials to be rotated and managed from outside the pipeline or team, and prevents them from being revealed by get-pipeline.
For more information, see Credential Management in Concourse.
Concourse provides options for team authorization to protect confidential or sensitive data.
For more information, see Configuring Team Authentication.
Monitoring and Troubleshooting
Concourse can emit metrics about both the system health itself and about the builds that it is running. Operators can tap into these metrics in order to observe the health of the system.
For more information, see Monitoring and Troubleshooting.
Concourse is composed of two major sub-components: the web service (ATC and TSA) and workers.
For information about the architecture of Concourse and its components, see Concourse Architecture.
Monitoring and Troubleshooting Your Installation
To troubleshoot your Pivotal Concourse installation, see Troubleshooting.
BOSH Concourse Compatibility
|Concourse Version||PostgreSQL||Tested Stemcell||Supported Stemcells||Tested CredHub|
|v5.2.0||9.6+ External||Xenial 315.26||315.x||2.4.0|
|v5.2.1||9.6+ External||Xenial 315.26||315.x||2.4.0|
|v5.2.3||9.6+ External||Xenial 315.26||315.x||2.4.0|
|v5.2.4||9.6+ External||Xenial 315.26||315.x||2.4.0|
|v5.5.3||9.6+ External||Xenial 456.27||456.x||2.4.0|
Helm Concouse Compatibility
|Concourse Version||PostgreSQL||Tested PKS||Tested Helm||Tested Kubectl|
If you are using PostgreSQL v11.1 or v11.2, set
0. This corrects a PostgreSQL infinite parallel query issue.
For more information, see max_parallel_workers_per_gather (integer) and BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query in the PostgreSQL documentation.
Concourse is compatible with CredHub versions 2.1.2 and later. It is not compatible with versions 2.0.0 to 2.1.1.
The values in the "Tested" columns indicate that Concourse was tested with the listed stemcell or product version upon release. This does not mean that Concourse is restricted to those dependencies.
For more information about the open source Concourse project that powers Pivotal Concourse, see the Concourse documentation.