Add java-buildpack cf-release release guide - #666
Open
stokpop wants to merge 1 commit into
Open
Conversation
Documents the cf-release side of cutting a buildpack release: the trigger-buildpack-pipeline -> dev-release -> deploy -> cats -> ship-it -> publish path, using java-buildpack 5.0.6 as a worked example. Aimed at team members doing a release for the first time, and written for the Concourse web UI rather than fly. Covers three things that are easy to get wrong: - ship-it is shared across all buildpacks. It writes one shared trigger file, so any buildpack whose cats-passed RC is ahead of its published version publishes too, not only yours. - publish is not a second button; it fires automatically a few minutes after ship-it. A missing publish nearly always means ship-it was not pressed. - create-cf-infrastructure-and-execute-integration-test-for-java runs 5-12h on a parallel branch and is not a gate, so the guide documents it as a manual check. The switchblade specs do gate the release, via detect-new-version-and-upload-artifacts. Job names, timings and gating were checked against the live pipelines.
wayneeseguin
approved these changes
Jul 17, 2026
wayneeseguin
left a comment
wayneeseguin
left a comment
There was a problem hiding this comment.
I've read through it, some things are surprising to me like all of the build packs being tied together for shipping. Other than that surprise it looks good to me.
kiril-keranov
approved these changes
Aug 28, 2026
kiril-keranov
left a comment
kiril-keranov
left a comment
Contributor
There was a problem hiding this comment.
looks good, just minor comment
| A release crosses two pipelines: | ||
|
|
||
| 1. **`java-buildpack`** builds and ships the buildpack, producing a GitHub | ||
| release tagged `v5.0.6`. |
Contributor
There was a problem hiding this comment.
can be pointed that v5.0.6 is an example release version
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/cf-release-buildpack-guide.md: how to cut a buildpack releasethrough the
cf-releasepipeline, with java-buildpack 5.0.6 as the workedexample. Written for a first-timer, via the Concourse UI rather than
fly.Covers three things that are easy to get confused:
ship-itis shared across all buildpacks. One shared trigger file, soany buildpack whose cats-passed RC is ahead of its published version
publishes too -- not only yours. Includes a read-only way to check first.
publishis not a second button. It fires automatically aftership-it. A missing publish nearly always meansship-itwas not pressed.create-cf-infrastructure-and-execute-integration-test-for-javais not agate. It runs 5-12h on a parallel branch, so the release does not wait on
it; the guide documents it as a manual check. The switchblade specs do gate
the release, via
detect-new-version-and-upload-artifacts.Complements #665, which documents the buildpack pipeline but not
cf-release, CATS, or the shared trigger. The reference tobuildpack-release-pipeline-overview.mdis plain text until #665 merges.Job names, timings and gating checked against the live pipelines.