From cbf8bbc875ad5755984a129d83d8b424146e9722 Mon Sep 17 00:00:00 2001 From: Aidan Delaney Date: Mon, 28 Oct 2024 10:14:43 +0000 Subject: [PATCH] Setup basic lifecycle orchastration test Create test suite and build `lifecycle` Signed-off-by: Aidan Delaney Signed-off-by: Aidan Delaney --- .../tutorials/lifecycle/_index.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/content/docs/for-platform-operators/tutorials/lifecycle/_index.md b/content/docs/for-platform-operators/tutorials/lifecycle/_index.md index 0a09a2d74..9eb34028a 100644 --- a/content/docs/for-platform-operators/tutorials/lifecycle/_index.md +++ b/content/docs/for-platform-operators/tutorials/lifecycle/_index.md @@ -9,6 +9,24 @@ A `platform` orchestrates builds by invoking the [lifecycle][lifecycle] binary t + + + + + + + + The majority of Buildpack users use community-maintained platforms, such as [pack][pack] and [kpack][kpack], to run Buildpacks and create `OCI images`. However this might not be desireable especially for users maintaining their own platforms and seeking more control over how the underlying Buildpack `lifecycle phases` are executed. > This tutorial is derived from a [blog post][blog post] contributed by one of our community members. @@ -44,6 +62,14 @@ As a starting step, you need to build the `lifecycle` in order to use its phases * `make build-linux-amd64` for `AMD64` architectures (for Linux users) * `make build-darwin-arm64` for `ARM64` architectures (for Mac users) + + + It's recommended to check the [lifecycle releases][releases] page to download binaries based on your system. > Please note that the entire process is most easily followed on Linux systems