What is Pivotal Concourse?
Concourse is a continuous integration tool that lets you build, scale, and monitor pipelines outside of your PCF 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 a BOSH release that 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.
Note: Use the BOSH CLI v2 or v3 with Pivotal Concourse. Pivotal does not recommend using the old BOSH CLI v1 with Pivotal Concourse.
When you are ready to get started, see the guide to Installing Pivotal Concourse.
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.
In order to protect confidential or sensitive data, Concourse provides options for team authorization.
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
If you're having trouble with your Pivotal Concourse installation, this topic may help.
For more information, see Troubleshooting.
|Concourse Version||RunC||PostgreSQL||Tested Stemcell||Supported Stemcells||Tested CredHub|
|v4.2.1||1.16.3||9.5+ External||Xenial 97.16||97.x||1.9.5|
|v4.2.2||1.16.0 & 1.17.2||9.5+ External||Xenial 97 & 170.13||97.x & 170.x||1.9.5|
|v4.2.3||1.18.2||9.5+ External||Xenial 250.9||250.x||1.9.5|
|v4.2.4||1.19.1||9.5+ External||Xenial 250.38||250.x||1.9.5|
|v4.2.5||1.19.1||9.5+ External||Xenial 250.38||250.x||1.9.5|
|v4.2.6||1.19.1||9.5+ External||Xenial 250.38||250.x||1.9.5|
|v4.2.7||1.19.8||9.5+ External||Xenial 456.51||456.x||1.9.5|
If you are using PostgreSQL v11.1 or v11.2, you must set
0. This will correct a PostgreSQL infinite parallel query bug.
For more information on
max_parallel_workers_per_gather, see max_parallel_workers_per_gather (integer) in the PostgreSQL documentation.
For more information on the PostgreSQL infinite parallel query bug, see BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query in the PostgreSQL documentation.
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.
You can also read the documentation for the open source Concourse project, which powers Pivotal Concourse.