lifecycle v0.3.0

lifecycle v0.3.0

This is the third beta release of the Cloud Native Buildpack Lifecycle. This implementation should be relatively stable and reliable, but breaking changes in the underlying specification may be implemented without notice.

Prerequisites

The lifecycle runs as a normal user in a series of unprivileged Linux containers. To export images and cache image layers, it requires access to a Docker daemon or Docker registry.

Install

Extract the .tgz file and copy the lifecycle binaries into a build stack base image. The build image can then be orchestrated by a platform implementation such as the pack CLI or knative.

Features

• Add support for exporting an image to multiple repositories or tags on the same registry (#140).
• Analyzer now permits skipping launch layer metadata restoration with -skip-layers flag.
• Avoid race conditions when previous image changes during the build (#20).

lifecycle v0.2.1

lifecycle v0.2.1

This is a patch to the second beta release of the Cloud Native Buildpack Lifecycle. This implementation should be relatively stable and reliable, but breaking changes in the underlying specification may be implemented without notice.

Prerequisites

The lifecycle runs as a normal user in a series of unprivileged Linux containers. To export images and cache image layers, it requires access to a Docker daemon or Docker registry.

Install

Extract the .tgz file and copy the lifecycle binaries into a build stack base image. The build image can then be orchestrated by a platform implementation such as the pack CLI or knative.

Fixes

• Fix critical bug that results in a failure to restore layer metadata to the correct location (#137).
• Move detection results to the beginning of each line (#134).

lifecycle v0.2.0

lifecycle v0.2.0

This is the second beta release of the Cloud Native Buildpack Lifecycle. This implementation should be relatively stable and reliable, but breaking changes in the underlying specification may be implemented without notice.

Prerequisites

The lifecycle runs as a normal user in a series of unprivileged Linux containers. To export images and cache image layers, it requires access to a Docker daemon or Docker registry.

Install

Extract the .tgz file and copy the lifecycle binaries into a build stack base image. The build image can then be orchestrated by a platform implementation such as the pack CLI or knative.

Key Features

• Implements Cloud Native Buildpack Specification as of buildpacks/spec@92a2673 as well as more recently added version constraints.
• Better error messages (#130, #135).
• Introduce launch-cache to improve performance when exporting to a daemon (#131 -> #132).
• Add Makefile (#129).
• Use stack.toml for run image (#127).
• Extract buildpack/imgutil package (#118 -> #125).
• Buildpack versions are constrained according to spec (#96).
• Support caching using volumes (e.g., PVCs) (#117, #120).
• Fix credential helper logic (#111).
• Improve logging for detection (#112).
• Add image creation time to images (#113).

lifecycle v0.1.0

lifecycle v0.1.0

This is the first beta release of the Cloud Native Buildpack Lifecycle. This implementation should be relatively stable and reliable, but breaking changes in the underlying specification may be implemented without notice.

Prerequisites

The lifecycle runs as a normal user in a series of unprivileged Linux containers. To export images and cache image layers, it requires access to a Docker daemon or Docker registry.

Install

Extract the .tgz file and copy the lifecycle binaries into a build stack base image. The build image can then be orchestrated by a platform implementation such as the pack CLI or knative.

Key Features

• Implements Cloud Native Buildpack Specification as of buildpacks/spec@92a2673.
• Implements complete avoidance of unnecessary layer re-builds and re-uploads.
• Implements image-based caching option (#83)
• Allows untrusted buildpacks and/or app code to be built in unprivileged containers without access to registry credentials.
• Enables reproducible builds by clearing timestamps (#108).
• Provides relevant logs (#80, #97, #98).
• Compatible with various Docker registry credential helpers (#43).

Known Issues

• This release does not support PVC-based caching in knative build templates. This will be addressed in the next patch release.