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.ymlfile in the root of the application directory with structure:
buildpacks:
- https://github.com/cloudfoundry/go-buildpack
- https://github.com/cloudfoundry/ruby-buildpack/releases/download/v1.6.23/ruby_buildpack-cached-v1.6.23.zip
- https://github.com/cloudfoundry/nodejs-buildpack#v1.5.18
- https://github.com/cloudfoundry/python-buildpack#develop-
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.ymlfile will not work:
buildpacks:
- ruby_buildpack
- go_buildpackBuildpacks 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 https://api.your-cf.com -u name@example.com -p pa55woRDNote 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:
-
Source the .envrc file in the buildpack directory.
source .envrcTo simplify the process in the future, install direnv which will automatically source .envrc when you change directories.
-
Run unit tests
./scripts/unit.sh
-
Run integration tests
./scripts/integration.sh
More information can be found on Github cutlass.
Find our guidelines here.
Join the #buildpacks channel in our Slack community if you need any further assistance.
Please fill out the issue template fully if you'd like to start an issue for the buildpack.
The project backlog is on Pivotal Tracker.