Concourse for PCF (Beta)
IMPORTANT: The Concourse for PCF tile is currently in beta and is intended for evaluation and test purposes only. Do not use this product in a PCF production environment.
This guide is intended for Pivotal Cloud Foundry (PCF) operators and developers who want to install and use the Concourse for PCF tile. To learn more about Concourse and access Concourse product documentation, see the Concourse CI website.
The Concourse for PCF tile provides on-demand service instances of Concourse in PCF environments. The tile relies on the On-Demand Services SDK.
The following table provides version and version-support information about Concourse for PCF:
|Version||Beta 2 (v1.0.0-edge.9)|
|Release date||February 2017|
|Compatible Ops Manager version(s)||v1.8.x, v1.9.x|
|Compatible Elastic Runtime version(s)||v1.8.x, v1.9.x|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
Concourse for PCF provides the following key features on top of open-source Concourse:
Service instance mapping of orgs and spaces to Concourse teams: PCF developers provision dedicated Concourse service instances for their PCF orgs and spaces. Creating a Concourse for PCF service instance automatically generates an associated Concourse team within that org and space. Any space can have multiple service instances and teams.
Horizontal and vertical scalability: Developers can specify the size and number of worker VMs for their service instance through the Cloud Foundry Command Line Interface (cf CLI). Operators define the service plans in PCF Operations Manager (Ops Manager).
Security: Users Authenticate through UAA (OAuth2). This integrates with Concourse teams and ensures that developers can only see and edit pipelines for the teams, orgs, and spaces to which they belong.
Please provide any bugs, feature requests, or questions to the PCF Feedback list.