jfrog rt cli upload folder and subfolder windows 10

Branch	Status
v2
dev
v1
dev-v1

Tabular array of Contents

• Overview
• Download and Installation
• Building the Executable
• Tests
• Code Contributions
• Using JFrog CLI
• JFrog CLI Plugins
• Release Notes

Overview

JFrog CLI is a meaty and smart client that provides a simple interface that automates admission to Artifactory and Mission Command through their corresponding REST APIs. By using the JFrog CLI, you tin can greatly simplify your automation scripts making them more readable and easier to maintain. Several features of the JFrog CLI makes your scripts more efficient and reliable:

• Multi-threaded upload and download of artifacts brand builds run faster
• Checksum optimization reduces redundant file transfers
• Wildcards and regular expressions requite you an easy style to collect all the artifacts you lot wish to upload or download.
• "Dry run" gives you a preview of file transfer operations before y'all actually run them

Download and Installation

You can either install JFrog CLI using one of the supported installers or download its executable straight. Visit the Install JFrog CLI Page for details.

Building the Executable

JFrog CLI is written in the Go programming linguistic communication, and so to build the CLI yourself, you start need to have Get installed and configured on your car.

Install Go

To download and install Become, please refer to the Go documentation. Please download Become 1.14.10 or higher up.

Download and Build the CLI

Navigate to a directory where you lot want to create the jfrog-cli projection, outside the $GOPATH tree.

If the GOPATH variable is unset, information technology's default value is the become folder under the user abode.

Verify that the GO111MODULE variable is either unset, or explicitly fix to car.

Clone the jfrog-cli project by executing the following command:

              git clone https://github.com/jfrog/jfrog-cli                          

Build the project past navigating to the jfrog folder and executing the post-obit commands. On Unix based systems run:

              cd jfrog-cli build/build.sh                          

On Windows run:

              cd jfrog-cli build\build.bat                          

Once completed, you volition find the JFrog CLI executable at your current directory.

Tests

Usage

              go test -five github.com/jfrog/jfrog-cli [test-types] [flags]                          

The flags are:

Flag	Clarification
-jfrog.url	[Default: http://localhost:8081] JFrog platform URL.
-jfrog.user	[Default: admin] JFrog platform username.
-jfrog.password	[Default: password] JFrog platform password.
-jfrog.adminToken	JFrog platform admin token.
-ci.runId	[Optional] A unique identifier used as a suffix to create repositories and builds in the tests.

The types are:

Type	Description
-test.artifactory	Artifactory tests
-test.npm	Npm tests
-exam.maven	Maven tests
-test.gradle	Gradle tests
-test.docker	Docker tests
-examination.become	Become tests
-test.pip	Pip tests
-test.pipenv	Pipenv tests
-test.nuget	Nuget tests
-test.plugins	Plugins tests
-exam.distribution	Distribution tests
-test.xray	Xray tests

• Running the tests volition create builds and repositories with timestamps, for instance: cli-rt1-1592990748 and cli-rt2-1592990748.
  Once the tests are completed, the content of these repositories will be deleted.

Artifactory tests

In improver to full general optional flags you can use the following optional artifactory flags.

Flag	Description
-jfrog.sshKeyPath	[Optional] Ssh key file path. Should be used only if the Artifactory URL format is ssh://[domain]:port.
-jfrog.sshPassphrase	[Optional] Ssh central passphrase.

Examples

To run artifactory tests execute the following command.

              go test -v github.com/jfrog/jfrog-cli -examination.artifactory [flags]                          

Npm tests

Requirements

• The npm executables should be included as role of the PATH environment variable.
• The tests are compatible with npm 7 and higher.

Limitation

• Currently, npm integration support only http(due south) connections to Artifactory using username and countersign.

Examples

To run npm tests execute the post-obit command.

              go test -five github.com/jfrog/jfrog-cli -exam.npm [flags]                          

Maven tests

Requirements

• The java executable should be included as part of the PATH environment variable. Alternatively, set the JAVA_HOME environment variable.

Limitation

• Currently, maven integration support only http(s) connections to Artifactory using username and password.

Examples

To run maven tests execute the following command.

              get test -v github.com/jfrog/jfrog-cli -test.maven [flags]                          

Gradle tests

Requirements

• The gradle executables should be included as office of the PATH environs variable.
• The coffee executable should exist included every bit part of the PATH environment variable. Alternatively, set the JAVA_HOME environment variable.

Limitation

• Currently, gradle integration support only http(s) connections to Artifactory using username and password.

Examples

To run gradle tests execute the following command.

              get test -v github.com/jfrog/jfrog-cli -test.gradle [flags]                          

Docker tests

In addition to general optional flags you must use the post-obit docker flags.

Requirements

• On Linux machines, Podman tests will be running, then make sure it's available in the local path.

Flag	Description
-rt.dockerRepoDomain	Artifactory Docker registry domain.
-rt.dockerVirtualRepo	Artifactory Docker virtual repository name.
-rt.dockerRemoteRepo	Artifactory Docker remote repository name.
-rt.dockerLocalRepo	Artifactory Docker local repository name.
-rt.dockerPromoteLocalRepo	Artifactory Docker local repository proper noun - Used for promotion.

Examples

To run docker tests execute the following command (fill out the missing parameters equally described below).

              go test -5 github.com/jfrog/jfrog-cli -test.docker -rt.dockerRepoDomain=DOCKER_DOMAIN -rt.DockerLocalRepo=DOCKER_LOCAL_REPO [flags]                          

Become commands tests

Requirement

• The tests are uniform with Artifactory 6.10 and college.
• To run get tests run the post-obit command:

              go exam -v github.com/jfrog/jfrog-cli -exam.become [flags]                          

NuGet tests

Requirement

• Add NuGet executable to the arrangement search path (PATH surroundings variable).
• Run the following command:

              go examination -5 github.com/jfrog/jfrog-cli -examination.nuget [flags]                          

Pip tests

Requirement

• Add Python and pip executables to the organisation search path (PATH environment variable).
• Run the following control:

              go test -v github.com/jfrog/jfrog-cli -test.pip [flags]                          

Plugins tests

To run Plugins tests execute the following command:

              become examination -v github.com/jfrog/jfrog-cli -test.plugins                          

Distribution tests

To run Distribution tests execute the post-obit command:

              go exam -v github.com/jfrog/jfrog-cli -examination.distribution [flags]                          

Xray tests

To run Xray tests execute the following command:

              go test -5 github.com/jfrog/jfrog-cli -test.xray [flags]                          

Lawmaking Contributions

Nosotros welcome code contributions through pull requests from the community.

Pull Requests Guidelines

• If the existing tests exercise not already cover your changes, please add together tests..
• Pull requests should be created on the dev co-operative.
• Delight use gofmt for formatting the code before submitting the pull asking.

Using JFrog CLI

JFrog CLI can be used for a diverseness of functions with Artifactory, Xray and Mission Control, and has a dedicated set up of commands for each production. To acquire how to use JFrog CLI, please visit the JFrog CLI User Guide.

JFrog CLI Plugins

JFrog CLI plugins support enhancing the functionality of JFrog CLI to meet the specific user and organisation needs. The source code of a plugin is maintained as an open source Become projection on GitHub. All public plugins are registered in JFrog CLI's Plugins Registry, which is hosted in the jfrog-cli-plugins-reg GitHub repository. We encourage you, as developers, to create plugins and share them publically with the rest of the community. Read more than near this in the JFrog CLI Plugin Developer Guide.

Release Notes

The release notes are available here.

davenportbehimphe.blogspot.com

Source: https://githubplus.com/jfrog/jfrog-cli

Share this post