Concourse for PCF Release Notes

IMPORTANT: The Concourse for PCF tile is currently in Beta and is meant for evaluation and test purposes only. Do not use this product in a PCF production environment.

This topic contains release notes for the Concourse for Pivotal Cloud Foundry (PCF) tile.

Beta 2 (v1.0.0-edge.9)

Release date: February 2017

This release of the Concourse for PCF tile contains the following components:

  • Concourse v2.6.0
  • On-Demand Broker v0.14.1
  • runC v1.0.4

Features

This release includes the following features:

  • Ability to configure a URL for the HTTP/HTTPS Proxy.
  • Support for three on-demand service plans (Beta 1 limited to one plan only).
  • ODB performs safer rolling upgrades of Concourse instances because workers wait for builds to finish before exiting.
  • Support for basic auth when creating or updating an instance:
    • The new parameters for cf create-service are --basic-auth-username and --basic-auth-password.

Known Issues

Deleting a service instance using cf delete-service destroys the corresponding VMs but does not delete the team in Concourse.

Beta 1 (v1.0.0-edge.7)

Release date: December 2016

Components

This release of the Concourse for PCF tile contains the following components:

  • Concourse v2.5.1
  • On-Demand Broker v0.10.1
  • runC v1.0.3

Features

This release includes the following features:

  • Multi-tenancy on PCF
    • PCF Developers can provision dedicated Concourse service instances (worker pool VMs) for their PCF orgs and spaces. See Creating Concourse Instances.
  • Horizontal and Vertical Scalability
    • Developers can specify the number of worker VMs and for their service instances with the cf CLI when they provision an instance.
    • Operators define service plans in Ops Manager, which specify the size of the VMs on the IaaS layer. See Step 6: Configure Service Plans in the installation topic.
  • Secure by default
    • All inter-component communication to and from the ATC, TSA, Broker, and workers require authenticated TLS connections.

      Note: Concourse for PCF supports self-signed certs for development purposes only.

  • oAuth flow and integration with Concourse teams
    • UAA integration: A PCF developer can only see and edit pipelines for Concourse teams in the PCF spaces where they have the Space Developer role.
    • Github integration: Users can authenticate using a Github oAuth flow through membership to specific Github orgs and teams.

Known Issues

The following list describes the known issues for this release:

  • The current version of Concourse does not support proper draining of in-flight jobs. As a result, any pipelines that have builds in-flight during an upgrade of the tile are likely to fail/error. To avoid any build disruption, Pivotal recommends pausing pipelines and letting all the in-flight builds finish before you start the tile upgrade process.
  • Deleting a service instance using cf delete-service destroys the corresponding VMs but does not delete the team in Concourse.
  • Any teams with Github authentication enabled may lose the ability to login with Github after a tile upgrade. As a temporary fix, you must re-enable Github for previously created teams using the fly set-team command.
Create a pull request or raise an issue on the source for this page in GitHub