Add release bundle docs under Deploy/Release Strategy. #3072
Conversation
This file contains 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
cmfcruz
force-pushed
the
add-release-bundle-docs
branch
from
ae11510 to
c5bfc54
Compare
|
Website deployed to CF Pages, 👀 preview link https://6420059b.balenacloud-docs.pages.dev |
cmfcruz
force-pushed
the
add-release-bundle-docs
branch
from
c5bfc54 to
0cd55b2
Compare
Change-type: minor Signed-off-by: Carlo Miguel F. Cruz <[email protected]>
cmfcruz
force-pushed
the
add-release-bundle-docs
branch
from
0cd55b2 to
e7cc2a3
Compare
| excerpt: Use the same release across multiple fleets using release bundles | ||
| --- | ||
|
|
||
| # Identical releases across multiple fleets |
There was a problem hiding this comment.
To bring it as more of an action word, how about we do the title as
Share releases with multiple fleets
|
|
||
| It is common to use multiple fleets on {{$names.company.lower}} to organize application development and fleet operations. Some users dedicate fleets to development and testing, pushing only tested code to production fleets. Others may use a "canary" fleet with a subset of production devices for additional testing before full deployment. | ||
|
|
||
| Testing can take time, and building a release from the same source may produce a different image than before due to updated external dependencies or mutable Dockerfile base images (e.g., latest). Consequently, a release built later might behave differently. |
There was a problem hiding this comment.
nit
Suggested change
| Testing can take time, and building a release from the same source may produce a different image than before due to updated external dependencies or mutable Dockerfile base images (e.g., latest). Consequently, a release built later might behave differently. | |
| Testing can take time, and building a release from the same source may produce a different image than before due to updated external dependencies or mutable Dockerfile base images (e.g. latest). Consequently, a release built later might behave differently. |
|
|
||
| Testing can take time, and building a release from the same source may produce a different image than before due to updated external dependencies or mutable Dockerfile base images (e.g., latest). Consequently, a release built later might behave differently. | ||
|
|
||
| To ensure the exact version of a tested release is deployed across fleets, you can export a release bundle file from an app, block, or fleet. This bundle allows you to import an identical copy of the release into another fleet. Unlike [{{$names.company.lower}} deploy][balena-deploy], which pushes images built locally, importing a release doesn't require a Docker engine on your machine. |
There was a problem hiding this comment.
Suggested change
| To ensure the exact version of a tested release is deployed across fleets, you can export a release bundle file from an app, block, or fleet. This bundle allows you to import an identical copy of the release into another fleet. Unlike [{{$names.company.lower}} deploy][balena-deploy], which pushes images built locally, importing a release doesn't require a Docker engine on your machine. | |
| To ensure the exact version of a tested release is deployed across fleets, you can export a release bundle file from an app, block, or fleet. This bundle allows you to import an identical copy of the release into another app, block, or fleet. Unlike [{{$names.company.lower}} deploy][balena-deploy], which pushes images built locally, importing a release doesn't require a Docker engine on your machine. |
|
|
||
| ## Importing a Release | ||
|
|
||
| You can import a release from a release bundle into a {{$names.company.lower}} app, block, or fleet. This creates the release in the specified fleet with the version defined in the release manifest within the release bundle. Additionally, the images for the release are uploaded to the registry during the import process. |
There was a problem hiding this comment.
Suggested change
| You can import a release from a release bundle into a {{$names.company.lower}} app, block, or fleet. This creates the release in the specified fleet with the version defined in the release manifest within the release bundle. Additionally, the images for the release are uploaded to the registry during the import process. | |
| You can import a release from a release bundle into a {{$names.company.lower}} app, block, or fleet. This creates the release in the specified app, block, or fleet with the version defined in the release manifest within the release bundle. Additionally, the images for the release are uploaded to the registry during the import process. |
|
|
||
| You can import a release from a release bundle into a {{$names.company.lower}} app, block, or fleet. This creates the release in the specified fleet with the version defined in the release manifest within the release bundle. Additionally, the images for the release are uploaded to the registry during the import process. | ||
|
|
||
| __Note:__ The revision number of the release's semantic version (semver) will not be set on the imported release. This number is automatically iterate by the {{$names.company.lower}} API when a release with the same semantic version already exists in the app, block, or fleet. |
There was a problem hiding this comment.
Suggested change
| __Note:__ The revision number of the release's semantic version (semver) will not be set on the imported release. This number is automatically iterate by the {{$names.company.lower}} API when a release with the same semantic version already exists in the app, block, or fleet. | |
| __Note:__ The revision number of the release's semantic version (semver) will not be set on the imported release. This number is automatically iterated by the {{$names.company.lower}} API when a release with the same semantic version already exists in the app, block, or fleet. |
|
|
||
| __Note:__ The revision number of the release's semantic version (semver) will not be set on the imported release. This number is automatically iterate by the {{$names.company.lower}} API when a release with the same semantic version already exists in the app, block, or fleet. | ||
|
|
||
| Releases can be imported to multiple fleets. A new fleet can be created, and a release from an older fleet can be imported into it. |
There was a problem hiding this comment.
A new fleet can be created, and a release from an older fleet can be imported into it.
Not sure what the purpose of this sentence is 🤔 Seems obvious to me but idk
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Change-type: minor