Updating buildpack related gems in Cloud Foundry
Page last updated:
buildpack-packager packages buildpacks and
machete provides an integration test framework.
The CF Buildpacks team uses the gems-and-extensions pipeline to:
- Run integration tests for
- Update the gems in the buildpacks managed by the team.
Running the update process
The following steps assume you are using a Concourse deployment of the
At the end of the process, there is a new GitHub release. Updates are then applied to the buildpacks.
To update the version of either gem in a buildpack:
- Verify that the test job
<gemname>-specsfor the gem was updated successfully and ran on the commit you plan to update.
<gemname>-tagjob to update (“bump”) the version of the gem.
<gemname>-releasejob starts and creates a new GitHub release of the gem.
Each of the buildpack pipelines, for example, the [go-buildpack pipeline,(https://buildpacks.ci.cf-app.com/teams/main/pipelines/go-buildpack)) has a job that watches for new releases of the gem. When a new release is detected, the buildpack’s
cf.Gemfileis updated to that release version.
The commit made to the buildpack’s
cf.Gemfilestarts the full integration test suite for that buildpack.
The final step starts all buildpack test suites simultaneously, and causes contention for available shared BOSH lite test environments.View the source for this page in GitHub