Cloud Foundry buildpack for running multiple buildpacks
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin Update go version for git buildpack Aug 26, 2017
fixtures Update ruby version in fixture Sep 14, 2017
scripts Simplify build/test scripts to make easier to run Nov 10, 2017
src/compile Require in Gopkg.toml Feb 15, 2018
.DS_Store Initial golang multi buildpack Feb 24, 2017
.envrc Simplify build/test scripts to make easier to run Nov 10, 2017
.gitallowed Update libbuildpack May 23, 2017
.gitignore Set GOBIN in .envrc Jul 20, 2017
CHANGELOG add Apache 2.0 license and note CLA requirements Sep 13, 2016
LICENSE add Apache 2.0 license and note CLA requirements Sep 13, 2016
PULL_REQUEST_TEMPLATE Create ISSUE_TEMPLATE and PULL_REQUEST_TEMPLATE Dec 23, 2016 Improve information about running integration tests [#154216032] Jan 16, 2018

Cloud Foundry Multi-buildpack

CF Slack Join us on Slack

The multi-buildpack buildpack provides older Cloud Foundry deployments with the same multi-buildpack support that is available in Cloud Foundry's CAPI v3 API. See Understanding Buildpacks for more info.


  • This buildpack looks for a multi-buildpack.yml file in the root of the application directory with structure:
  • The multi-buildpack will download + run all the buildpacks in this list in the specified order.

  • It will use the app start command given by the final buildpack (the last buildpack in your multi-buildpack.yml).

  • The multi-buildpack buildpack will not work with system buildpacks. You must use URLs as shown above. Ex. the following multi-buildpack.yml file will not work:

  - ruby_buildpack
  - go_buildpack


Buildpacks use the Cutlass framework for running integration tests against Cloud Foundry. Before running the integration tests, you need to login to your Cloud Foundry using the cf cli:

cf login -a -u -p pa55woRD

Note that your user requires permissions to run cf create-buildpack and cf update-buildpack. To run the integration tests, run the following commands from the buildpack's directory:

  1. Source the .envrc file in the buildpack directory.

    source .envrc

    To simplify the process in the future, install direnv which will automatically source .envrc when you change directories.

  2. Run unit tests

  3. Run integration tests


More information can be found on Github cutlass.


Find our guidelines here.

Help and Support

Join the #buildpacks channel in our Slack community if you need any further assistance.

Reporting Issues

Please fill out the issue template fully if you'd like to start an issue for the buildpack.

Active Development

The project backlog is on Pivotal Tracker.