Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update release-lifecycle-management.md #173

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -98,16 +98,18 @@ The file spec may be of one of the following creation sources:
|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Command-name | release-bundle-create |
| Abbreviation | rbc |
| **Command arguments:** | |
| **Command arguments:** | |
| release bundle name | Name of the newly created Release Bundle. |
| release bundle version | Version of the newly created Release Bundle. |
| **Command options:** | |
| `--project` | <p>[Optional]<br>Project key associated with the created Release Bundle version.</p> |
| `--server-id` | <p>[Optional]<br>Platform Server ID configured using the 'jf config' command.</p> |
| `--signing-key` | <p>[Mandatory]<br>The GPG/RSA key-pair name given in Artifactory.</p> |
| `--spec` | <p>[Optional]<br>Path to a File Spec.</p> |
| `--spec-vars` | <p>[Optional]<br>List of semicolon-separated(;) variables in the form of "key1=value1;key2=value2;..." (wrapped by quotes) to be replaced in the File Spec. In the File Spec, the variables should be used as follows: ${key1}.</p> |
| `--sync` | <p>[Default: false]<br>Set to true to run synchronously.</p> | |
| **Command options:** | |
| `--project` | <p>[Optional]<br>Project key associated with the created Release Bundle version.</p> |
| `--server-id` | <p>[Optional]<br>Platform Server ID configured using the 'jf config' command.</p> |
| `--signing-key` | <p>[Mandatory]<br>The GPG/RSA key-pair name given in Artifactory.</p> |
| `--spec` | <p>[Optional]<br>Path to a File Spec.</p> |
| `--build-name` | <p>[Optional]<br>Build name to create the bundle from./p> | |
| `--build-number` | <p>[Optional]<br>Build number to create the bundle from.</p> | |
| `--spec-vars` | <p>[Optional]<br>List of semicolon-separated(;) variables in the form of "key1=value1;key2=value2;..." (wrapped by quotes) to be replaced in the File Spec. In the File Spec, the variables should be used as follows: ${key1}.</p> |
| `--sync` | <p>[Default: false]<br>Set to true to run synchronously.</p> | |

### Examples
#### Example 1
Expand All @@ -134,6 +136,14 @@ Create a release bundle using file spec variables.
jf rbc --spec=/path/to/spec.json --spec-vars="key1=value1" --signing-key=myKeyPair myApp 1.0.0
```

#### Example 3

Create a release bundle using build name and number variables.

```
jf rbc --build-name=Common-builds --build-number=1.0.0 myApp 1.0.0
```

## Promoting a release bundle

This command allows promoting a release bundle to a target environment.
Expand Down
Loading