Skip to content

Lifecycle/support multiple sources #207

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.

Sign up for GitHub

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

Merged
rimapol merged 5 commits into from
Jul 2, 2025
Merged

Lifecycle/support multiple sources #207

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7f350ea
Introduce annotate command into release-lifecycle-management
rimapol May 12, 2025
2925b37
Code review changes
rimapol May 12, 2025
269c270
Merge branch 'jfrog:main' into main
rimapol Jun 26, 2025
fb4ce9d
Merge branch 'jfrog:main' into main
rimapol Jul 2, 2025
9555aa1
Introduce support multiple source for create release bundle
rimapol Jul 2, 2025
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
120 changes: 106 additions & 14 deletions ...pplications/jfrog-cli/cli-for-jfrog-artifactory/release-lifecycle-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,24 +93,90 @@ The **create** command allows creating a Release Bundle v2 using [file specs](ht

Only a single AQL query may be provided.

* Specified package (one or more):
```
{
"files": [
{
"package": "catalina",
"version":"1.0.0",
"type": "maven",
"repoKey": "catalina-dev-maven-local"
},
]
}
```

* A Release Bundle created from multiple sources:
The Release Bundle can include any number of builds, artifacts (using a pattern), packages, and Release Bundles.
However, it can include only one AQL query:
```
{
"files": [
{
"build": "Commons-Build/1.0.0",
"includeDeps":"true",
"project": "default"
},
{
"bundle": "rb1/1.0.0",
"project": "default"
},
{
"bundle": "rb4/1.0.0",
"project": "default"
},
{
"pattern": "catalina-dev-maven-local/*.jar"
},
{
"package": "commons",
"version":"1.0.1",
"type": "maven",
"repoKey": "commons-dev-maven-local"
},
{
"package": "catalina",
"version":"1.0.0",
"type": "maven",
"repoKey": "catalina-dev-maven-local"
},
{
"aql": {
"items.find": {
"repo":{"$eq":"catalina-dev-maven-local"},
"$and":[
{"name": {"$match":"*1.0.0.pom"}}
]
}
}
}
]
}
```


### Command Params

| | |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Command-name | release-bundle-create |
| Abbreviation | rbc |
| | |
| ------------------ |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Command-name | release-bundle-create |
| Abbreviation | rbc |
| **Command arguments:** | |
| release bundle name | Name of the newly created Release Bundle. |
| 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>[Optional]<br>The GPG/RSA key-pair name defined in Artifactory. The <code>signing-key</code> can also be configured as an environment variable. If no key is specified, Artifactory uses a default key.</p> |
| `--spec` | <p>[Optional]<br>Path to a File Spec. If you do not define the spec, you must include the <code>build-name</code> and <code>build-number</code> as environment variables, flags, or a combination of both (flags override environment variables).</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> |
| `--build-name` | <p>[Optional]<br>The name of the build from which to create the Release Bundle.</p> |
| `--build-number` | <p>[Optional]<br>The number of the build from which to create the Release Bundle.</p> |
| `--sync` | <p>[Default: true]<br>Set to false to run asynchronously.</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>[Optional]<br>The GPG/RSA key-pair name defined in Artifactory. The <code>signing-key</code> can also be configured as an environment variable. If no key is specified, Artifactory uses a default key.</p> |
| `--spec` | <p>[Optional]<br>Path to a File Spec. If you do not define the spec, you must include the <code>build-name</code> and <code>build-number</code> as environment variables, flags, or a combination of both (flags override environment variables).</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> |
| `--build-name` | <p>[Optional]<br>The name of the build from which to create the Release Bundle.</p> |
| `--build-number` | <p>[Optional]<br>The number of the build from which to create the Release Bundle.</p> |
| `--source-type-release-bundles`| <p>[Optional]<br>One or more Release Bundles to include in the new Release Bundle in the form of "name=[rb-name], version=[rb-version];..." .</p> |
| `--source-type-builds` | <p>[Optional]<br>One or more builds to include in the new Release Bundle in the form of "name=[build-name], id=[build-id], include-deps=[true/false];...".</p> |
| `--sync` | <p>[Default: true]<br>Set to false to run asynchronously.</p> |


### Examples

Expand Down Expand Up @@ -138,6 +204,32 @@ Create a Release Bundle using build name and build number variables.
jf rbc --build-name=Common-builds --build-number=1.0.0 myApp 1.0.0
```

#### Example 4

Create a Release Bundle from multiple builds

```
jf rbc rb3 1.0.0 --source-type-builds "name=Commons-Build, id=1.0.0, include-deps=true; name=Commons-Build, id=1.0.1"
```

#### Example 5

Create a Release Bundle from multiple existing Release Bundles.

```
jf rbc rb3 1.0.0 --project catalina --source-type-release-bundles "name=rb1, version=1.0.0; name=rb2, version=1.0.0"
```

#### Example 6

Create a Release Bundle from existing builds and Release Bundles.

```
jf rbc rb3 1.0.0 --source-type-builds "name=Commons-Build, id=1.0.0, include-deps=true; name=Commons-Build, id=1.0.1"
--source-type-release-bundles "name=rb1, version=1.0.0; name=rb2, version=1.0.0"
```


## Promote a Release Bundle v2

This command allows promoting a Release Bundle to a target environment.
Expand Down