CAUTION: Pivotal does not provide support for these pipelines. If you find anything broken, then please submit a PR.
This repository provides the pipelines for the products listed in the following table.
PIVOTAL PRODUCT NAME | VERSION | PIPELINE LOCATION |
---|---|---|
Isolation Segments | 2.1.x | Isolation Segments Installation |
RabbitMQ | 1.12.x | RabbitMQ Installation |
Redis | 1.12.x | Redis Installation |
Spring Cloud Services | 1.5.x | Spring Cloud Services Installation |
MySQL-v1 | 1.10.x | MySQL-v1 Installation [TO BE DISCONTINUED] |
MySQL-v2 | 2.2.x | MySQL-v2 Installation |
PCF Metrics | 1.4.x | PCF Metrics Installation |
Healthwatch | 1.2.x | Healthwatch Installation |
Splunk Nozzle | 1.0.x | Splunk Nozzle Installation |
New Relic Nozzle | 1.0.x | New Relic Nozzle Installation |
New Relic Service Broker | 1.12.x | New Relic Service Broker Installation |
Spring Cloud Data Flow | 1.0.x | Spring Cloud Data Flow Installation |
Single Signon | 1.6.x | Single Signon Installation |
AppDynamics Service Broker | 4.4.135 | AppDynamics Service Broker Installation |
Upgrade Buildpacks | any | Upgrade Buildpacks |
Upgrade Tile | any | Upgrade Tile |
> fly -t concourse-[ENV] login -c https://<CONCOURSE-URL> -k
> fly -t concourse-[ENV] set-pipeline -p install-healthwatch -c ./pipelines/tiles/healthwatch/pipeline.yml -l ./pipelines/tiles/healthwatch/params.yml
> fly -t concourse-[ENV] unpause-pipeline -p install-healthwatch
Once the pipeline executes successfully, there will be a new pipeline set in the concourse based on the concourse information provided in the params file of the install pipeline. Make sure your concourse instance requires authentication, failing which the set-upgrade-pipeline
job will fail.