You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/CLI-for-JFrog-Artifactory.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,7 @@ jf rt u "(*).tgz" my-local-repo/{1}/ --recursive=false
140
140
141
141
Upload all files whose name begins with "frog" to folder **frogfiles** in the target repository, but append its name with the text "-up". For example, a file called **froggy.tgz** should be renamed **froggy.tgz-up**.
142
142
```
143
-
jf u "(frog*)" my-local-repo/frogfiles/{1}-up --recursive=false
143
+
jf rt u "(frog*)" my-local-repo/frogfiles/{1}-up --recursive=false
144
144
```
145
145
146
146
##### **Example 3: Upload all files to corresponding directories according to extension type**
@@ -235,8 +235,8 @@ This command is used to upload files to Artifactory.
235
235
| --retry-wait-time |\[Default: 0s\]<br><br>Number of seconds or milliseconds to wait between retries. The numeric value should either end with s for seconds or ms for milliseconds. |
236
236
| --detailed-summary |\[Default: false\]<br><br>Set to true to include a list of the affected files as part of the command output summary. |
237
237
| --insecure-tls |\[Default: false\]<br><br>Set to true to skip TLS certificates verification. |
238
-
| Command arguments | The command takes two arguments.<br><br>In case the --spec option is used, the commands accept no arguments. |
239
-
| Source path | The first argument specifies the local file system path to artifacts that should be uploaded to Artifactory. You can specify multiple artifacts by using wildcards or a regular expression as designated by the **--regexp** command option. Please read the **--regexp** option description for more information. |
238
+
| Command arguments | The command takes two arguments.<br><br>In case the --spec option is used, the commands accept no arguments. |
239
+
| Source path | The first argument specifies the local file system path to artifacts that should be uploaded to Artifactory. You can specify multiple artifacts by using wildcards or a regular expression as designated by the **--regexp** command option. Please read the **--regexp** option description for more information. |
240
240
| Target path | The second argument specifies the target path in Artifactory in the following format: `[repository name]/[repository path]`<br><br>If the target path ends with a slash, the path is assumed to be a folder. For example, if you specify the target as "repo-name/a/b/", then "b" is assumed to be a folder in Artifactory into which files should be uploaded. If there is no terminal slash, the target path is assumed to be a file to which the uploaded file should be renamed. For example, if you specify the target as "repo-name/a/b", the uploaded file is renamed to "b" in Artifactory.<br><br>For flexibility in specifying the upload path, you can include placeholders in the form of {1}, {2} which are replaced by corresponding tokens in the source path that are enclosed in parenthesis. For more details, please refer to [Using Placeholders](https://jfrog.com/help/r/jfrog-cli/using-placeholders). |
Copy file name to clipboardExpand all lines: documentation/JFrog-CLI.md
+16-8
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ JFrog CLI supports uploading files to Artifactory using wildcard patterns, regul
18
18
19
19
JFrog CLI offers comprehensive support for popular package managers and build tools. It seamlessly integrates with package managers like npm, Maven, NuGet, Docker and more, allowing you to easily manage and publish packages.
20
20
21
-
### Binaries and depedencies scanning
21
+
### Binaries and dependencies scanning
22
22
23
23
JFrog CLI empowers you with robust scanning capabilities to ensure the security and compliance of your software artifacts, including containers. It integrates with JFrog Xray, enabling you to scan and analyze your projects and packages, including containers, for vulnerabilities, license compliance, and quality issues. With JFrog CLI, you can proactively identify and mitigate potential risks, ensuring the integrity and safety of your software supply chain.
24
24
@@ -292,7 +292,7 @@ JFrog CLI makes use of the following environment variables:
| **JFROG_CLI_LOG_LEVEL** | \[Default: INFO\]<br><br>This variable determines the log level of the JFrog CLI. <br>Possible values are: DEBUG, INFO, WARN and ERROR. <br>If set to ERROR, JFrog CLI logs error messages only. It is useful when you wish to read or parse the JFrog CLI output and do not want any other information logged. |
295
+
| **JFROG_CLI_LOG_LEVEL** | \[Default: INFO\]<br><br>This variable determines the log level of the JFrog CLI. <br>Possible values are: DEBUG, INFO, WARN and ERROR. <br>If set to ERROR, JFrog CLI logs error messages only. It is useful when you wish to read or parse the JFrog CLI output and do not want any other information logged. |
296
296
| **JFROG_CLI_LOG_TIMESTAMP** | \[Default: TIME\]<br><br>Controls the log messages timestamp format. Possible values are: TIME, DATE\_AND\_TIME, and OFF. |
297
297
| **JFROG_CLI_HOME_DIR** | \[Default: ~/.jfrog\]<br><br>Defines the JFrog CLI home directory. |
298
298
| **JFROG_CLI_TEMP_DIR** | \[Default: The operating system's temp directory\]<br><br>Defines the temp directory used by JFrog CLI. |
@@ -304,9 +304,17 @@ JFrog CLI makes use of the following environment variables:
304
304
305
305
## JFrog Platform Configuration
306
306
307
+
### Web Login to the JFrog Platform
308
+
309
+
You can use the `jf login` command to authenticate with the JFrog Platform through the web browser.
310
+
This command is solely interactive, meaning it does not receive any options and cannot be used in a CI server.
The **config add** and **config edit** commands are used to add and edit JFrog Platform server configuration, stored in JFrog CLI's configuration storage. These configured servers can be used by the other commands. The configured servers' details can be overridden per command by passing in alternative values for the URL and login credentials. The values configured are saved in file under the JFrog CLI home directory.
317
+
The `jf config add` and `jf config edit` commands are used to add and edit JFrog Platform server configuration, stored in JFrog CLI's configuration storage. These configured servers can be used by the other commands. The configured servers' details can be overridden per command by passing in alternative values for the URL and login credentials. The values configured are saved in file under the JFrog CLI home directory.
| --overwrite | \[Available for _config add_ only\]<br><br>\[Default: false\]<br><br>Overwrites the instance configuration if an instance with the same ID already exists. |
340
+
| --overwrite | \[Available for `jf config add` only\]<br><br>\[Default: false\]<br><br>Overwrites the instance configuration if an instance with the same ID already exists. |
333
341
| Command arguments | |
334
342
| server ID | A unique ID for the server configuration. |
335
343
336
344
### Removing Configured Servers
337
345
338
-
The _config remove_ command is used to remove JFrog Platform server configuration, stored in JFrog CLI's configuration storage.
346
+
The `jf config remove` command is used to remove JFrog Platform server configuration, stored in JFrog CLI's configuration storage.
@@ -348,7 +356,7 @@ The _config remove_ command is used to remove JFrog Platform server configuratio
348
356
349
357
### Showing the Configured Servers
350
358
351
-
The _config show_ command shows the stored configuration. You may show a specific server's configuration by sending its ID as an argument to the command.
359
+
The `jf config show` command shows the stored configuration. You may show a specific server's configuration by sending its ID as an argument to the command.
@@ -369,7 +377,7 @@ The _config use_ command sets a configured server as default. The following comm
369
377
370
378
### Exporting and Importing Configuration
371
379
372
-
The _config export_ command generates a token, which stores the server configuration. This token can be used by the _config import_ command, to import the configuration stored in the token, and save it in JFrog CLI's configuration storage.
380
+
The `jf config export` command generates a token, which stores the server configuration. This token can be used by the `jf config import` command, to import the configuration stored in the token, and save it in JFrog CLI's configuration storage.
0 commit comments