README
¶
release deploy
Deploy a release into production.
Usage
salsaflow release deploy [-release=VERSION]
Description
Deploy the selected release into production.
The release to be deployed can be selected in the following ways:
- The
releasecommand line flag selectsVERSIONas the release to be deployed. That's it. - When no release is specified manually, SalsaFlow prompts the user to select one of the releases that were stages since the previous deployment. In other words, it lists the tags that were created since the current stable branch position.
There are some checks in place so that you cannot simply deploy any release.
Well, actually, the release flag cancels all checks, so it should be used
with caution, but for the selection mode of release deploy, SalsaFlow will
only list the releases that are suitable for being deployed. This usually means
that all associated stories were accepted. But it's not as simple as that.
SalsaFlow will never list a release that happened after a release that is not
releasable so that it is not possible to deploy stories that were not accepted.
Steps
This command goes through the following steps:
- Make sure the stable branch exists and is up to date.
- Select the release to be deployed. Prompt the user in case the release is not specified explicitly.
- Reset the stable branch to point to the tag associated with the given release.
- Push the stable branch to the remote repository. This is expected to trigger deployment (or any post-release step that makes sense for the project).
Documentation
¶
Overview ¶
Deploy a release into production.
salsaflow release deploy [-release=VERSION]
Description ¶
Deploy the selected release into production.
The release to be deployed can be selected in the following ways:
- The -release command line flag selects VERSION as the release to be deployed. That's it.
- When no release is specified manually, SalsaFlow prompts the user to select one of the releases that were staged since the previous deployment. In other words, it lists the tags that were created since the current stable branch position.
There are some checks in place so that you cannot simply deploy any release. Well, actually, the -release flag cancels all checks, so it should be used with caution, but for the selection mode of release deploy, SalsaFlow will only list the releases that are suitable for being deployed. This usually means that all associated stories were accepted. But it's not as simple as that. SalsaFlow will never list a release that happened after a release that is not releasable so that it is not possible to deploy stories that were not accepted.
Steps ¶
This command goes through the following steps:
- Make sure the stable branch exists and is up to date.
- Select the release to be deployed. Prompt the user in case the release is not specified explicitly.
- Reset the stable branch to point to the tag associated with the given release.
- Push the stable branch to the remote repository. This is expected to trigger deployment (or any post-release step that makes sense for the project).
Index ¶
Constants ¶
This section is empty.
Variables ¶
var Command = &gocli.Command{
UsageLine: "deploy [-release=VERSION]",
Short: "deploy a release into production",
Long: `
Deploy the chosen release into production.
This basically means that the stable branch is reset
to point to the relevant release tag, then force pushed.
In case the release is not specified explicitly, the user is offered
the releases that can be deployed. These are the releases that happened
after the current stable branch position. On top of that,
all associated stories must be accepted.
In case the release is specified on the command line, no additional checks
are performed and the stable branch is reset and pushed. USE WITH CAUTION!
`,
Action: run,
}
Functions ¶
This section is empty.
Types ¶
This section is empty.
Source Files