Skip to content

Commit 6901a29

Browse files
rimapolrimapol
authored
Lifecycle/support multiple sources (#207)
1 parent bdacfd9 commit 6901a29

1 file changed

Lines changed: 106 additions & 14 deletions

File tree

‎jfrog-applications/jfrog-cli/cli-for-jfrog-artifactory/release-lifecycle-management.md‎

Lines changed: 106 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -93,24 +93,90 @@ The **create** command allows creating a Release Bundle v2 using [file specs](ht
9393
9494
Only a single AQL query may be provided.
9595
96+
* Specified package (one or more):
97+
```
98+
{
99+
"files": [
100+
{
101+
"package": "catalina",
102+
"version":"1.0.0",
103+
"type": "maven",
104+
"repoKey": "catalina-dev-maven-local"
105+
},
106+
]
107+
}
108+
```
109+
110+
* A Release Bundle created from multiple sources:
111+
The Release Bundle can include any number of builds, artifacts (using a pattern), packages, and Release Bundles.
112+
However, it can include only one AQL query:
113+
```
114+
{
115+
"files": [
116+
{
117+
"build": "Commons-Build/1.0.0",
118+
"includeDeps":"true",
119+
"project": "default"
120+
},
121+
{
122+
"bundle": "rb1/1.0.0",
123+
"project": "default"
124+
},
125+
{
126+
"bundle": "rb4/1.0.0",
127+
"project": "default"
128+
},
129+
{
130+
"pattern": "catalina-dev-maven-local/*.jar"
131+
},
132+
{
133+
"package": "commons",
134+
"version":"1.0.1",
135+
"type": "maven",
136+
"repoKey": "commons-dev-maven-local"
137+
},
138+
{
139+
"package": "catalina",
140+
"version":"1.0.0",
141+
"type": "maven",
142+
"repoKey": "catalina-dev-maven-local"
143+
},
144+
{
145+
"aql": {
146+
"items.find": {
147+
"repo":{"$eq":"catalina-dev-maven-local"},
148+
"$and":[
149+
{"name": {"$match":"*1.0.0.pom"}}
150+
]
151+
}
152+
}
153+
}
154+
]
155+
}
156+
```
157+
158+
96159
### Command Params
97160
98-
| | |
99-
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
100-
| Command-name | release-bundle-create |
101-
| Abbreviation | rbc |
161+
| | |
162+
| ------------------ |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
163+
| Command-name | release-bundle-create |
164+
| Abbreviation | rbc |
102165
| **Command arguments:** | |
103-
| release bundle name | Name of the newly created Release Bundle. |
166+
| release bundle name | Name of the newly created Release Bundle. |
104167
| release bundle version | Version of the newly created Release Bundle. |
105-
| **Command options:** | |
106-
| `--project` | <p>[Optional]<br>Project key associated with the created Release Bundle version.</p> |
107-
| `--server-id` | <p>[Optional]<br>Platform Server ID configured using the 'jf config' command.</p> |
108-
| `--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> |
109-
| `--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> |
110-
| `--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> |
111-
| `--build-name` | <p>[Optional]<br>The name of the build from which to create the Release Bundle.</p> |
112-
| `--build-number` | <p>[Optional]<br>The number of the build from which to create the Release Bundle.</p> |
113-
| `--sync` | <p>[Default: true]<br>Set to false to run asynchronously.</p> |
168+
| **Command options:** | |
169+
| `--project` | <p>[Optional]<br>Project key associated with the created Release Bundle version.</p> |
170+
| `--server-id` | <p>[Optional]<br>Platform Server ID configured using the 'jf config' command.</p> |
171+
| `--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> |
172+
| `--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> |
173+
| `--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> |
174+
| `--build-name` | <p>[Optional]<br>The name of the build from which to create the Release Bundle.</p> |
175+
| `--build-number` | <p>[Optional]<br>The number of the build from which to create the Release Bundle.</p> |
176+
| `--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> |
177+
| `--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> |
178+
| `--sync` | <p>[Default: true]<br>Set to false to run asynchronously.</p> |
179+
114180
115181
### Examples
116182
@@ -138,6 +204,32 @@ Create a Release Bundle using build name and build number variables.
138204
jf rbc --build-name=Common-builds --build-number=1.0.0 myApp 1.0.0
139205
```
140206
207+
#### Example 4
208+
209+
Create a Release Bundle from multiple builds
210+
211+
```
212+
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"
213+
```
214+
215+
#### Example 5
216+
217+
Create a Release Bundle from multiple existing Release Bundles.
218+
219+
```
220+
jf rbc rb3 1.0.0 --project catalina --source-type-release-bundles "name=rb1, version=1.0.0; name=rb2, version=1.0.0"
221+
```
222+
223+
#### Example 6
224+
225+
Create a Release Bundle from existing builds and Release Bundles.
226+
227+
```
228+
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"
229+
--source-type-release-bundles "name=rb1, version=1.0.0; name=rb2, version=1.0.0"
230+
```
231+
232+
141233
## Promote a Release Bundle v2
142234
143235
This command allows promoting a Release Bundle to a target environment.

0 commit comments

Comments
 (0)