jfrog / setup-jfrog-cli Goto Github PK

View Code? Open in Web Editor NEW

235.0 29.0 71.0 2.53 MB

Set up JFrog CLI in your GitHub Actions workflow

License: Apache License 2.0

JavaScript 43.43% TypeScript 56.43% Shell 0.14%

actions jfrog jfrog-cli jfrog-artifactory jfrog-xray jf-artifactory bintray

setup-jfrog-cli's Issues

Better Authentication Options

Hey 👋 Firstly, love the GitHub Action! Really nice 👍

The one thing that I don't like about this action though is the section: creating-the-configuration-on-your-local-machine.

Is there any way to generate this programmatically vs having a user input. We want to use this action but we would like to rotate this credential every 24 hours for security reason. We would like to create a custom GitHub Action that creates the credential and updates the GitHub Secret which THIS action would be using for authentication (hopefully that makes sense).

In a perfect world, I would just send you my Artifactory URL and Access Token.

Also:

jfrog rt c

This is deprecated in the latest CLI.

I think it would be good to just pass in the Artifacotry URL and Artifactory Access Token.

Additionally, the reason why I want to use an access token is I would like to scope the access token to just be what I want ti to be, vs everything 👍

Would love to discuss thoughts and ideas around this 💯

What is --server-id?

Hi,
please give a real example of what the server-id variable looks like.

My xray server is: artifactory.congo123.com/xray
My Artifactory is: artifactory.congo123.com/artifactory

what is --server-id ?

Using GITHUB_RUN_NUMBER Environment Variable Instead of Commit Hash

Hi,

I would like to suggest using the ${GITHUB_RUN_NUMBER} environment variable instead of the commit hash as the build number published to JFrog Artifactory.

From it's description it sounds like it might fit better:

"A unique number for each run of a particular workflow in a repository. This number begins at 1 for the workflow's first run, and increments with each new run. This number does not change if you re-run the workflow run."

Hope my feedback helps!

Tal

Upgrade to 1.0.3 breaks

[Error] This operation requires Docker version 17.07.0 or higher.
##[error]Process completed with exit code 1.

When I go back to 1.0.2 I'm able to run builds.

Certificate is Expired

Describe the bug

We're using the jfrog cli setup and getting the following errors when downloading the CLI from the releases page.

Current behavior

Setup JFrog CLI
  Downloading JFrog CLI from https://releases.jfrog.io/artifactory/jfrog-cli/v2/2.52.9/jfrog-cli-linux-amd64/jfrog
  certificate has expired
  Waiting [12](REDACTED/actions/runs/7569598/jobs/17729308?pr=6371#step:7:13) seconds before trying again
  certificate has expired
  Waiting 19 seconds before trying again
  Error: certificate has expired

Reproduction steps

No response

Expected behavior

No response

Setup JFrog CLI version

JFrog CLI version

2.52.9

Workflow operating system type and version

Linux

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

Using jfrog/setup-jfrog-cli without internet access

Is your feature request related to a problem? Please describe.
We have noticed that this action calls out to the internet to download the latest cli files. We use GitHub Enterprise Server, and due to company restrictions, we cannot access the internet from our action, therefore this action is currently a problem for us. Here’s an example of where the remote url to download the jfrog cli is hardcoded.

https://github.com/jfrog/setup-jfrog-cli/blob/master/src/utils.ts

Describe the solution you'd like to see
Can we add a parameter to specify the location (internal) to download the CLI? For example:

- uses: jfrog/setup-jfrog-cli@v2
  with:
    - path: https://internallocation.mycompany.com/jfrog-cli

Describe alternatives you've considered
One alternative is to fork and make the change ourselves, but we'd prefer to use the public action. We suspect there are others with similar requirements who would benefit from this.

Upgrade JFrog CLI version to address Maven 3.9.x incompatibility

Is your feature request related to a problem? Please describe.

I confirm this issue has been resolved. Tested with 2.39.1
jfrog/jfrog-cli#1964

Describe the solution you'd like to see

Upgrade to a Jfrog CLI version which has support for Maven 3.9.x.
Latest version as of the opening of this ticket is [2.42.1](https://github.com/jfrog/jfrog-cli/releases/tag/v2.42.1)

Describe alternatives you've considered

No response

Additional context

No response

Integrate with tool cache

Usually most of these setup actions which download something also integrates with actions toolkit cache. Then cli would be resolved from a cache and no need to download from a Bintray.

Now that Bintray has been down most of a morning(all my actions using cli fails), this cache in most cases would prevent failures when cli cannot be downloaded.

JFrog CLI with Certificates Doesn't Work with GitHub Action

JFrog CLI with Certificates Not Working with GitHub Actions
My Artifactory instance is configured to use a certificate. Hence while configuring JFrog CLI, I have to provide the Client Certificate Path and Client Certificate Key Path. Both these are local paths (say C:\Path-of-certificate). I am running jfrog cli on Windows 10 and the cli is the latest (1.47.1). After this, I exported this token and created an org level secret and used it in my workflow. While trying to do jfrog rt ping, it is trying to locate the certificate from a physical path specified during rt cli configuration.

To Reproduce
Use Client Certificate and Key Path during CLI configuration

Versions

Setup JFrog CLI version: 1.47.1
Workflow operating system: ubuntu-latest
JFrog CLI version: 1.47.1
Artifactory Version: 7.12.8

setup-jfrog-cli should be added with latest JFrog CLI as default version

Is your feature request related to a problem? Please describe.
If we want to enjoy the latest fixes and new features and be update to date with JFrog CLI version, we need to manually add the version in the workflow.
Describe the solution you'd like to see
It would be great if setup-jfrog-cli will have the default JFrog CLI version as the latest version.
Describe alternatives you've considered
We can achieve this by modifying the workflow with the latest version of JFrog CLI manually.
uses: jfrog/setup-jfrog-cli@v1
with:
version: X.Y.Z
Additional context

Unable to fetch the latest version when using --build flag

Describe the bug
When trying to download the artifacts from Arifactory using Jfrog CLI and specifying the --build option and it is expected to fetch the latest version but it is not fetching the latest version.

To Reproduce
Steps to reproduce the issue:
Uploaded 3 artifacts to Artifactory in the following order:

EDP-edp-libraries-854115_20210310.1.tar.gz
EDP-edp-libraries-1152295_20210602.1.tar.gz
EDP-EDP-libraries-1163740_20210604.1.tar.gz
To upload the package and publish the build, we can use the below command:
jfrog rt u EDP-edp-libraries-854115_20210310.1.tar.gz divija-build-test --build-name=EDP-edp-libraries --build-number=854115_20210310.1
jfrog rt bp EDP-edp-libraries 854115_20210310.1

jfrog rt u EDP-edp-libraries-1152295_20210602.1.tar.gz divija-build-test --build-name=EDP-edp-libraries --build-number=1152295_20210602.1
jfrog rt bp EDP-edp-libraries 1152295_20210602.1

jfrog rt u EDP-edp-libraries-1163740_20210604.1.tar.gz divija-build-test--build-name=EDP-edp-libraries --build-number=1163740_20210604.1
jfrog rt bp EDP-edp-libraries 1163740_20210604.1

Downloaded the packages from Artifactory using JFrog CLI:
When we download the package using the below command:
jfrog rt dl divija-build-test/ --build EDP-edp-libraries*

with "--build EDP-edp-libraries" option --> the first uploaded package (854115_20210310.1.tar.gz) is resolved instead of the latest pacakge (1163740_20210604.1.tar.gz).

According to the documentationhttps://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-DownloadingFiles, it says when we use --build flag and If we do not specify the build number, the artifacts are filtered by the latest build number. So we are expecting to get the latest artifact version.

Expected behavior
It is expected to download the latest artifact version that was published. In our case latest package (1163740_20210604.1.tar.gz) should be resolved instead of the first uploaded package (854115_20210310.1.tar.gz)

Screenshots

Versions

JFrog CLI version: 1.48.1
Artifactory Version: 7.19.8

Hardcoded `v1` path prevents usage of `v2` cli

Describe the bug
Version 2 of the CLI is out, and recommended for usage. It is unable to be used with this action.

To Reproduce

setup-jfrog-cli/src/utils.ts

Line 42 in cd5a0e8

    
           return 'https://releases.jfrog.io/artifactory/jfrog-cli/v1/' + version + '/' + architecture + '/' + fileName;

Expected behavior
JFROG_CLI_VERSION should be respected, regardless of version.

Versions

Setup JFrog CLI version: 1.2.0
Workflow operating system: ubuntu
JFrog CLI version: any 2.0

can not use jfrogcli action in rocky 9/ubi9

Describe the bug

when i use docker image (rocky9 and ubi9) as action runner when use jfrog cli action the error message is :
Download action repository 'actions/checkout@v2' (SHA:7884fcad6b5d53d10323aee724dc68d8b9096a2e)
Download action repository 'jfrog/setup-jfrog-cli@v3' (SHA:d0a59b1cdaeeb16e65b5039fc92b8507337f1559)
Warning: Failed to download action 'https://api.github.com/repos/jfrog/setup-jfrog-cli/tarball/d0a59b1cdaeeb16e65b5039fc92b8507337f1559'. Error: The SSL connection could not be established, see inner exception.
Warning: Back off 19.424 seconds before retry.
Warning: Failed to download action 'https://api.github.com/repos/jfrog/setup-jfrog-cli/tarball/d0a59b1cdaeeb16e65b5039fc92b8507337f[15]'. Error: The SSL connection could not be established, see inner exception.
Warning: Back off 23.234 seconds before retry.
Error: The SSL connection could not be established, see inner exception.

Current behavior

name: test-rocky-9
on:
workflow_dispatch:
permissions:
id-token: write
contents: read
env:
SHOW_STACK_TRACE: true
JFROG_CLI_LOG_LEVEL: "DEBUG"
jobs:
build:
runs-on: [ ubi ]
steps:
- uses: actions/checkout@v2
- name: download
run: |
yum install -y ca-certificates
update-ca-trust force-enable
- uses: jfrog/setup-jfrog-cli@v3
- run: jf --version

Warning: Failed to download action 'https://api.github.com/repos/jfrog/setup-jfrog-cli/tarball/d0a59b1cdaeeb16e65b5039fc92b8507337f1559'. Error: The SSL connection could not be established, see inner exception.
Warning: Back off 13.824 seconds before retry.
Error: The SSL connection could not be established, see inner exception.

Reproduction steps

No response

Expected behavior

No response

Setup JFrog CLI version

jfrog/setup-jfrog-cli@v3

JFrog CLI version

2.29.2

Workflow operating system type and version

rocky 9 and ubi 9

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

(short feature description)

Is your feature request related to a problem? Please describe.

The feature request is not related to an operational problem with the tool. It's a documentation enhancement.

Describe the solution you'd like to see

There is an undocumented, and quite useful, input to the Action for the OIDC integration. In the code, it's clear we can take in an input parameter called oidc-audience. I'd like to see this documented. This is an important configuration option that can make implementing the OIDC configuration in the JFrog Platform much easier for users.

      - name: Install JFrog CLI
        uses: jfrog/setup-jfrog-cli@v3
        env:
          JF_URL: ${{ vars.JF_URL }}
        with:
          oidc-provider-name: ${{ env.JF_OIDC_PROVIDER_NAME }}
          oidc-audience: ${{ env.OIDC_AUDIENCE }}

Describe alternatives you've considered

No response

Additional context

No response

node 12 deprecation

Is your feature request related to a problem? Please describe.
I'm getting this warning:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: jfrog/setup-jfrog-cli, jfrog/setup-jfrog-cli

Describe the solution you'd like to see
Upgrade to Node.js 16. Create new major version release to keep v2 compatible with Node.js 12.

Describe alternatives you've considered
None.

Additional context
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

OIDC integration does not work with Docker when the Identity Mapping is set to Group as the Token Scope on Artifactory's side

Describe the bug

When you have set the Artifactory OIDC integration to Group in Token Scope it will result in a the username of the format "oidc-provide/identity-mapping" on Artifactory's side but this integration will input the integration as "identity-mapping" this results in a docker pull failing because of the difference in expected usernames.

It fails with the error, "Wrong username was used" when trying to perform a docker login.

Current behavior

Docker pull will fail because the username is not the one that Artifactory expects.

As there is not a way to assign the username when using the token (JF_USER does not work), you will have to instead change the Token Scope to a user instead. You can assign that user only the needed group.

Reproduction steps

Set up the OIDC integration in Artifactory to use Group as the Token Scope.

Trigger a github action workflow that utilizes the OIDC token or authentication.
Note that this happens both with the JF_ACCESS_TOKEN (when utilizing the rest endpoint (access/api/v1/oidc/token) to retrieve the OIDC token) and also with the OIDC Authorization provided by this project. As an example in the following I just used OIDC Authorization method as it is shorter:

name: GitHub Actions Demo
on: [push]

permissions:
  contents: read
  id-token: write


jobs:
  build:
    runs-on: ubuntu-latest
    env:
      OIDC_AUDIENCE: 'jfrog-github'
      OIDC_PROVIDER: 'github'
      JFROG_CLI_LOG_LEVEL: 'DEBUG'
    steps:
      - name: Setup JFrog CLI
        uses: jfrog/setup-jfrog-cli@v4
        env:
          JF_URL: ${{ vars.JF_URL }}
        with:
          oidc-provider-name: ${{ env.OIDC_PROVIDER }}
          oidc-audience: ${{ env.OIDC_AUDIENCE }}
      - name: Check Access Token
        run: |
          jf config show
          jf config ex
      - name: Pull Docker image
        run: jf docker pull ${{ vars.JF_URLBASE}}/docker-docker/hello-world

Perform a docker pull and note the error:

Run jf docker pull ***/docker-docker/hello-world
18:50:20 [Debug] JFrog CLI version: 2.53.2
18:50:20 [Debug] OS/Arch: linux/amd64
18:50:20 [Debug] Sending HTTP GET request to: https://***/artifactory/api/system/version
18:50:20 [Debug] Artifactory response: 200 
18:50:20 [Debug] Sending HTTP GET request to: https://***/artifactory/api/system/version
18:50:20 [Debug] Usage Report: Sending info...
18:50:20 [Debug] Sending HTTP GET request to: https://***/artifactory/api/system/version
18:50:20 [Debug] Artifactory response: 200 
18:50:20 [Debug] Artifactory response: 200 
18:50:20 [Debug] JFrog Artifactory version is: 7.84.6
18:50:20 [Debug] Sending HTTP POST request to: https://***/artifactory/api/system/usage
18:50:20 [Debug] Using access-token details in docker-login command.
Error response from daemon: Get "https://***v2/": unknown: Wrong username was used
18:50:21 [Debug] docker login while assuming proxy-less failed: exit status 1
Error: 1 [Error] docker login failed for: ***.
docker image must be in the form: registry-domain/path-in-repository/image-name:version.
Error: Process completed with exit code 1.

Expected behavior

I expect this JFCLI integration to correctly input the username to what Artifactory expects.

Or less ideally allow the JF_USER to be set when utilizing JF_ACCESS_TOKEN or when using the OIDC Authorization.
i.e.

        with:
          oidc-provider-name: ${{ env.OIDC_PROVIDER }}
          oidc-audience: ${{ env.OIDC_AUDIENCE }}

Setup JFrog CLI version

jfrog/setup-jfrog-cli@v4

JFrog CLI version

2.53.2

Workflow operating system type and version

Github actions Current runner version: '2.316.0' Operating System Ubuntu 22.04.4 LTS

JFrog Artifactory version (if relevant)

7.84.6

JFrog Xray version (if relevant)

No response

Windows runner pwsh not exiting on invalid jf rt upload command

Describe the bug

The JFrog CLI when run under shell: pwsh should fail and exit when given an invalid jf rt upload ... command

For example:

on:
  push:
    branches:
      - main

jobs:
  test-exits-windows-normal-invalid-command:
    runs-on: windows-latest
    steps:
      - name: setup jfrog cli
        uses: jfrog/setup-jfrog-cli@v3

      - name: powershell actually exits on normal invalid command
        if: always()
        shell: pwsh
        run: |
          $ErrorActionPreference = 'Stop'
          someInvalidCommand
          jfrog rt --help


  test-exits-windows:
    runs-on: windows-latest
    steps:
      - name: setup jfrog cli
        uses: jfrog/setup-jfrog-cli@v3

      - name: powershell should also exit on invalid jfrog command
        if: always()
        shell: pwsh
        run: |
          $ErrorActionPreference = 'Stop'
          jfrog rt upload invalidcommand
          jfrog rt --help
  
  test-exits-linux:
    runs-on: ubuntu-latest
    steps:
      - name: setup jfrog cli
        uses: jfrog/setup-jfrog-cli@v3

      - name: Bash is fine and works correctly
        shell: bash
        run: |
          jfrog rt upload invalidcommand
          jfrog rt --help

results in

Notably, the passing step (which should be failing!) will correctly fail if the final line in the pwsh block is an invalid jfrog CLI command.

I believe that running a passing JFrog command (or any command?) after the failed command will cause the overall step to register as a pass.

Current behavior

invalid or incorrectly formatted jf rt upload ... commands, when run under shell: pwsh on windows runners do not exit.

Reproduction steps

run the workflow above

Expected behavior

invalid or incorrectly formatted jf rt upload ... commands, when run under shell: pwsh on windows runners should prevent the pwsh block from progressing.

Setup JFrog CLI version

uses: jfrog/setup-jfrog-cli@v3

JFrog CLI version

version: 2.50.4

Workflow operating system type and version

windows-latest

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

Github Actions : deprecated env command

As of Dec 1st, the GitHub actions pipelines using set-env were failing due to the change in the GitHub actions handling the environment vars.

version used: jfrog/[email protected]

Does the latest version of the jfrog action support environment files or is it still using set-env ? below are some of the failures noticed with the rt upload.

jf rt u source to destination says success but doesn't upload the artifact to the repository

Describe the bug

Working a demo with a simple goal of uploading a terraform module to Artifactory, the workflow file works fine and everything execute according to plan, but when checking the files at Artifactory it's not uploading, it says upload but doesn't count the success as 1.

Steps to reproduce:

GitHub Workflow file.

name: "github-repo-creation-workflow"

on:
  workflow_dispatch:
  push:
    branches:
      - main
jobs:
  Plan:
    name: Plan
    runs-on: ubuntu-latest
    steps:
      - name: Checkout out code
        uses: actions/checkout@v3
      - name: Set up terraform
        uses: hashicorp/setup-terraform@v2
      - name: Terraform fmt
        run: terraform fmt -recursive
      - name: terraform init
        run: terraform init
      - name: terraform plan
        run: terraform plan
      - name: save plan
        run: | 
          mkdir artifacts
          terraform plan -out=artifacts/file_provision.zip
      - name: upload artifact
        uses: actions/upload-artifact@v3
        with:
          name: terraform-plan
          path: artifacts/file_provision.zip
  Internal:
    name: Test JFrog Artifactory
    needs: Plan
    runs-on: [ubuntu-latest]
    steps:
      - name: download artifact
        uses: actions/download-artifact@v3
        with:
          name: terraform-plan
          path: artifacts/file_provision.zip
        
      - name: Display structure of downloaded files
        run: ls -R
        working-directory: artifacts
      - name: Setup JFrog
        uses: jfrog/setup-jfrog-cli@v3
        env:
          JF_URL: ${{ vars.JFROG_URL }}
          JF_ACCESS_TOKEN: ${{ secrets.JFROG_TF }}
      - name: ping artifactory
        run: |
          jf rt ping --insecure-tls
      - name: upload artifacts 
        run: jf rt u artifacts/file_provision.zip target-repo

Current behavior

Execute successfully but it doesn't upload the file.

Run jfrog/setup-jfrog-cli@v3
Setup JFrog CLI
1s
Run jf rt ping --insecure-tls
OK
[1](https://github.com/customer-demo/jfrog-demo/actions/runs/5485004767/jobs/9993263291#step:5:1)s
Run jf rt u artifacts/file_provision.zip generic-local
{
  "status": "success",
  "totals": {
    "success": 0,
    "failure": 0
  }
}

Reproduction steps

No response

Expected behavior

To upload the file.

Setup JFrog CLI version

latest version

JFrog CLI version

lastest version

Workflow operating system type and version

ubuntu

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

JFrog CLI not reading environment variables correctly

Describe the bug

A previously working reference to setup-jfrog-cli@v3 stopped working. The root cause is that the JF_URL environment variable does not appear to be recognized. The changed code is here: https://github.com/jfrog/setup-jfrog-cli/pull/117/files#diff-39b2554fd18da165b59a6351b1aafff3714e2a80c1435f2de9706355b4d32351R86

It looks like there are unit tests for this specific use case, I cannot tell from looking at the code exactly what is going wrong.

Current behavior

The following error:

Error: 'download-repository' input provided, but no JFrog environment details found. Hint - Ensure that the JFrog connection details environment variables are   Error: 'download-repository' input provided, but no JFrog environment details found. Hint - Ensure that the JFrog connection details environment variables are set: either a Config Token with a JF_ENV_ prefix or separate env config (JF_URL, JF_USER, JF_PASSWORD, JF_ACCESS_TOKEN)set: either a Config Token with a JF_ENV_ prefix or separate env config (JF_URL, JF_USER, JF_PASSWORD, JF_ACCESS_TOKEN)

Reproduction steps

We are using the action in the following GitHub Action job step:

- name: Setup JFrog CLI
        if: steps.validate.outcome == 'success'
        uses: jfrog/setup-jfrog-cli@v3
        env:
          JF_URL: https://artifactory.tools.bestbuy.com/
          JF_USER: ${{ env.ARTIFACTORY_USERNAME }}
          JF_ACCESS_TOKEN: ${{ env.ARTIFACTORY_ACCESS_TOKEN }}
        with:
          download-repository: generic-jfrog-cli-remote
          version: latest
``

### Expected behavior

Action to complete successfully.This action stopped working with the push of 3.5.0 a few hours ago and we solved issue by pinning version to 3.4.2. 

### Setup JFrog CLI version

3.5.0

### JFrog CLI version

default (2.52.7)

### Workflow operating system type and version

Ubuntu 22.04

### JFrog Artifactory version (if relevant)

Artifactory EnterpriseX 7.71.11

### JFrog Xray version (if relevant)

_No response_

certificate has expired

Describe the bug
When running this action, I see the following in the logs:

2022-02-18T12:11:17.8413288Z ##[group]Setup JFrog CLI
2022-02-18T12:11:18.2593575Z certificate has expired
2022-02-18T12:11:18.2596765Z Waiting 19 seconds before trying again
2022-02-18T12:11:37.5734329Z certificate has expired
2022-02-18T12:11:37.5735300Z Waiting 18 seconds before trying again
2022-02-18T12:11:55.9134550Z ##[error]certificate has expired
2022-02-18T12:11:55.9207334Z ##[endgroup]
2022-02-18T12:11:55.9353133Z Post job cleanup.
2022-02-18T12:11:56.0852828Z ##[group]Cleanup JFrog CLI servers configuration
2022-02-18T12:11:56.4663941Z certificate has expired
2022-02-18T12:11:56.4667119Z Waiting 14 seconds before trying again
2022-02-18T12:12:10.8074540Z certificate has expired
2022-02-18T12:12:10.8074846Z Waiting 16 seconds before trying again
2022-02-18T12:12:27.1351354Z ##[error]certificate has expired
2022-02-18T12:12:27.1371105Z ##[endgroup]
2022-02-18T12:12:27.1443759Z Post job cleanup.

To Reproduce
Configure the action like this in the GHA workflow:

      - uses: jfrog/setup-jfrog-cli@v1
        env:
          JF_ARTIFACTORY_1: <<redacted>>

Expected behavior
Tool is installed without error.

Screenshots
See logs, no other relevant info.

Versions

Setup JFrog CLI version: v1
Workflow operating system: linux
JFrog CLI version: ?
Artifactory Version: ?

Multiple GitHub Runners on self-hosted runner cause permission issue

How can we help?

Hello,

I run multiple self-hosted GitHub runners (github-runner1 - github-runner4) on the same machine. When I run this action a folder is generated under /tmp/jfrog which can only be accessed by the runner which created it, but any follow up workflow runs using other runners cause a "Permission denied" error, because they can't access the directory as it was generated by github-runner2 in that specific example.

user@server:~$ ls -l /tmp/jfrog/
total 4
drwxr-xr-x 3 github-runner2 github-runner2 4096 Apr 30 08:45 builds

Is there some way to specify the location of that folder with some environment variable or any other way to allow multiple runners on the same machine?

This is my action

name: build_app

on:
  workflow_dispatch:

jobs:
  build:
    runs-on: self-hosted
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Setup Artifactory
        uses: jfrog/setup-jfrog-cli@v4
        env:
          JF_URL: ${{ vars.JF_URL }}
          JF_ACCESS_TOKEN: ${{ secrets.JF_ACCESS_TOKEN }}
      - name: Build App
        run: echo "app" > app
      - name: Upload App
        run: jfrog rt u app sw-generic/

using this action with OIDC auth mechanism produces refreshable token

Describe the bug

Using this action per https://jfrog.com/blog/secure-access-development-jfrog-github-oidc/ results in a refreshable token being generated.

Current behavior

See above.

Reproduction steps

Use this action:

name: 'sample'
on: 'push'
permissions:
  id-token: 'write'
jobs:
  sample:
    runs-on: 'ubuntu-latest'
    steps:
      - uses: 'jfrog/setup-jfrog-cli@v4'
        env:
          JF_URL: '<JFrog Platform URL>'
        with:
          oidc-audience: 'jfrog-github' # magic strings that must align with JFrog GitHub OIDC integration
          oidc-provider-name: 'github' # magic strings that must align with JFrog GitHub OIDC integration

After, query access tokens via REST api or view them in web UI and see that the token issued for this job is refreshable.

Expected behavior

A non-refreshable token to be issued for this action which honors the configuration (including time to expiry) for the identity mapping that this action resolved to.

Setup JFrog CLI version

'jfrog/setup-jfrog-cli@v4' (SHA:d82fe26823e1f25529250895d5673f65b02af085)

JFrog CLI version

2.53.2

Workflow operating system type and version

Ubuntu 22.04.4 (runner version: '2.314.1')

JFrog Artifactory version (if relevant)

SaaS

JFrog Xray version (if relevant)

SaaS

Getting --url option is mandatory error for ping and upload commands

Describe the bug

I'm trying to upload in a GitHub Action with jfrog rt upload --spec build/upload_spec.json, and I get the --url option is mandatory error. I tried configuring the JFrog CLI with environment variables (JF_URL and JF_TOKEN), and also with the Config Token exported from my local setup (where the command works).

I tried even just running jfrog rt ping, and that also gives the same error.

If I add --url on on the command line, the ping command works, but the upload does not (get 401 Unauthorized).

Current behavior

This is the output from the jfrog/setup-jfrog-cli@v3 step

Run jfrog/setup-jfrog-cli@v3
  with:
    version: [2](https://github.com/REDACTED/actions/runs/4582980103/jobs/8093546472#step:12:2).[3](https://github.com/REDACTED/actions/runs/4582980103/jobs/8093546472#step:12:3)5.0
  env:
    BRANCH_NAME: 2/merge
    CI: true
    CHANGE_ID: 2
    BUILD_NUMBER: 18
    CHANGE_TARGET: master
    GITHUB_TOKEN: ***
    JFROG_CLI_LOG_LEVEL: DEBUG
    AWS_DEFAULT_REGION: us-east-2
    AWS_REGION: us-east-2
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
    AWS_SESSION_TOKEN: ***
    pythonLocation: /opt/actions-runner/_work/_tool/Python/3.7.16/x6[4](https://github.com/REDACTED/actions/runs/4582980103/jobs/8093546472#step:12:4)
    PKG_CONFIG_PATH: /opt/actions-runner/_work/_tool/Python/3.7.16/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/actions-runner/_work/_tool/Python/3.7.16/x64
    Python2_ROOT_DIR: /opt/actions-runner/_work/_tool/Python/3.7.16/x64
    Python3_ROOT_DIR: /opt/actions-runner/_work/_tool/Python/3.7.16/x64
    LD_LIBRARY_PATH: /opt/actions-runner/_work/_tool/Python/3.7.16/x64/lib
    JF_ENV_1: 
Setup JFrog CLI
  Downloading JFrog CLI from https://releases.jfrog.io/artifactory/jfrog-cli/v2/2.3[5](https://github.com/REDACTED/actions/runs/4582980103/jobs/8093546472#step:12:5).0/jfrog-cli-linux-amd[6](https://github.com/REDACTED/actions/runs/4582980103/jobs/8093546472#step:12:6)4/jfrog

This is the out put from my next step, which runs the JFrog CLI command

Run jfrog rt upload --spec build/upload_spec.json
11:56:56 [Debug] JFrog CLI version: 2.35.0
11:56:56 [Debug] OS/Arch: linux/amd64
11:56:56 [Debug] Locking config file to run config Clear command.
11:56:56 [Debug] Creating lock in: /home/ubuntu/.jfrog/locks/config
11:56:56 [Debug] Releasing lock: /home/ubuntu/.jfrog/locks/config/jfrog-cli.conf.lck.5874.1680350216994187067
11:56:56 [Debug] Config Clear command completed successfully. config file is released.
Error: 6 [Error] the --url option is mandatory
Error: Process completed with exit code 1.

When I run the jfrog rt ping command locally with the JFROG_CLI_LOG_LEVEL="DEBUG" flag set, I see successful HTTP GET commands and 200 responses.

Reproduction steps

I have this in my action:

      - name: Setup Jfrog CLI
        uses: jfrog/setup-jfrog-cli@v3
        env:
          JF_ENV_1: ${{ secrets.JF_SECRET_ENV_1 }}
#          JF_URL: ${{ secrets.ARTIFACTORY_URL }}
#          JF_ACCESS_TOKEN: ${{ secrets.ARTIFACTORY_TOKEN }}
      - name: Upload to Artifactory
        shell: bash
        run: jfrog rt upload --spec build/upload_spec.json

When I run the action, the Upload to Artifactory step fails with the error the --url option is mandatory. If I add the URL, I get 401 Unauthorized errors (which is the same thing that happens when I run the jfrog rt upload command locally with that flag). The same thing happens if I run with the Config Token (as shown above in the snip), or with the commented out JF_URL and JF_ACCESS_TOKEN env vars instead. I do not try to run with all 3 env vars set.

I created the admin-level access token in the Artifactory UI. We run a self-hosted installation of Artifactory, and do not use JFrog Platform.

Expected behavior

I expect to see something like this

{
  "status": "success",
  "totals": {
    "success": 1,
    "failure": 0
  }

And find my artifact in Artifactory.

Setup JFrog CLI version

@V3 (as of today, this is 3.2.0)

JFrog CLI version

I'm using the default, which is 2.35.0 as of today.

Workflow operating system type and version

linux/amd64 self-hosted runner, ubuntu-jammy-22.04

JFrog Artifactory version (if relevant)

self-hosted, 7.41.7

JFrog Xray version (if relevant)

N/A

version change in action.yaml to 2.50 cli version breaking the existing git workflows. commit https://github.com/jfrog/setup-jfrog-cli/commit/60f0b2eae7e0f3bc79c092fa43587f5592b07339

Describe the bug

Error: 7 [Error] Get "xxx.jfrog.io/artifactory/api/system/version": unsupported protocol scheme ""

We were using github command jfrog/setup-jfrog-cli@v3 with default version. So it was referring the cli version defined in https://github.com/jfrog/setup-jfrog-cli/blob/master/action.yml. Moment this version got updated from 2.44 to 2.50 . we observed that our github workflows started failing.

We recovered the failure by setting specific cli version to jfrog/setup-jfrog-cli@v3 as 2.44.1 and it started working.

Current behavior

We recovered the failure by setting specific cli version to jfrog/setup-jfrog-cli@v3 as 2.44.1 and it started working. but it fail for all the workflows which are relying on default version

following command used in the workflow

jf c add
jf docker tag
jf docker push
jf rt bce
jf rt bag
jf rt bp

Reproduction steps

mentioned above

Expected behavior

mentioned above

Setup JFrog CLI version

JFrog CLI version

v2.50

Workflow operating system type and version

linux

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

Artifactory returns 404 for private GitHub Docker Repository

Describe the bug

Artifactory always returns 404 for private GitHub repo where my docker image is deployed.

Current behavior

When configuring a remote docker repository in Artifactory as following:

URL: https://ghcr.io//
Username: PAT Name
Password: PAT (with read:packages permission) -> also already tried to give all permissions, but still same behaviour

With this configuration always 404 is returned, with following error message:
Connection failed: Target remote URL returned error 404: Not Found

In the logs I can find following entry:

2024-05-16T16:25:08.269Z [jfrt ] [WARN ] [3507df68c5423496] [c.p.ResponseProcessCookies:130] [http-nio-8081-exec-8] - Invalid cookie header: "Set-Cookie: _octo=GH1.1.774614533.1715876708; domain=github.com; path=/; expires=Fri, 16 May 2025 16:25:08 GMT; secure; SameSite=Lax". Invalid 'expires' attribute: Fri, 16 May 2025 16:25:08 GMT
2024-05-16T16:25:08.611Z [jfrt ] [WARN ] [3507df68c5423496] [c.p.ResponseProcessCookies:130] [http-nio-8081-exec-8] - Invalid cookie header: "Set-Cookie: _octo=GH1.1.1649066562.1715876708; domain=github.com; path=/; expires=Fri, 16 May 2025 16:25:08 GMT; secure; SameSite=Lax". Invalid 'expires' attribute: Fri, 16 May 2025 16:25:08 GMT
2024-05-16T16:25:08.720Z [jfrt ] [WARN ] [3507df68c5423496] [.r.c.s.ResearchServiceImpl:290] [http-nio-8081-exec-8] - We were unable to check repoType, maybe it does not exist

Reproduction steps

No response

Expected behavior

No response

Setup JFrog CLI version

JFrog CLI version

Workflow operating system type and version

Kubernetes 1.29

JFrog Artifactory version (if relevant)

Helm Chart version: 107.84.10

JFrog Xray version (if relevant)

No response

Authentication fails with version 4.0.2

Describe the bug

We are getting an 401 Unauthorized when using the version 4.0.2 of the action.

As far as I analyized the problem there seems something strange:

Output of the 4.0.2 setup step:

Setup JFrog CLI
  Downloading JFrog CLI from https://releases.jfrog.io/artifactory/jfrog-cli/v2/2.56.1/jfrog-cli-linux-amd64/jfrog
  /opt/hostedtoolcache/jf/2.56.1/x64/jf config add setup-jfrog-cli-server --url https://XXX --interactive=false --overwrite=true
Run jfrog/[email protected]
  with:
    version: 2.56.1
  env:
    JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/17.0.11-9/x6[4](https://github.com/XXX/maven-backend/actions/runs/9067734311/job/24947679824?pr=10#step:6:4)
    JAVA_HOME_17_X64: /opt/hostedtoolcache/Java_Zulu_jdk/17.0.11-9/x64
    JF_URL: XXX
    JF_ACCESS_TOKEN: 
Setup JFrog CLI
  Downloading JFrog CLI from https://releases.jfrog.io/artifactory/jfrog-cli/v2/2.5.6.1/jfrog-cli-linux-amd64/jfrog
  /opt/hostedtoolcache/jf/2.56.1/x64/jf config add setup-jfrog-cli-server --url https://XXX --interactive=false --overwrite=true

The same code with the 4.0.1 action has this diff:

  env:
    JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/17.0.11-9/x6[4](https://github.com/XXX/maven-backend/actions/runs/9067734311/job/24947679824?pr=10#step:6:4)
    JAVA_HOME_17_X64: /opt/hostedtoolcache/Java_Zulu_jdk/17.0.11-9/x64
    JF_URL: XXX
    JF_ACCESS_TOKEN: ***
[...]

/opt/hostedtoolcache/jf/2.53.2/x64/jf config add setup-jfrog-cli-server --url https://XXX --interactive=false --overwrite=true --access-token ***

There the token gets read from the secret and is passed to the jf config add-command

Current behavior

Accessing artifactory via jf commands are failing with 401 Unauthorized

Reproduction steps

action code:

      - name: Setup JFrog CLI
        uses: jfrog/[email protected]
        env:
          JF_URL: "https://artifactory.XXX.de"
          JF_ACCESS_TOKEN: ${{ secrets.ARTIFACTORY_TOKEN }}

      - name: Run any maven build which requires artifacts from artifactory
        run: |
          jf mvn-config ....

works.

v4.0.2 not

Expected behavior

mvn build is able to pull artifacts from protected artifactrory instances

Setup JFrog CLI version

whatever is installed by the action ;)

JFrog CLI version

whatever is installed by the action ;)

Workflow operating system type and version

linux

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

Exchanging JSON web token with an access token failed: Input required and not supplied: oidc-provider-name

Describe the bug

env variables are not recognized - regression in v3.5.0

githubenv variables are not recognized, causing fallback to OICD which fails with this error

Current behavior

2024-01-17T17:02:34.2039427Z ::group::Setup JFrog CLI
2024-01-17T17:02:34.2039979Z ##[group]Setup JFrog CLI
2024-01-17T17:02:34.2056995Z ##[debug]Searching for JF_URL
2024-01-17T17:02:34.2057524Z ##[debug]JF_URL found
2024-01-17T17:02:34.2058097Z ##[debug]Searching for JF_ACCESS_TOKEN, JF_USER and JF_PASSWORD
2024-01-17T17:02:34.2059057Z JF_ACCESS_TOKEN and JF_USER + JF_PASSWORD weren't found. Getting access token using OpenID Connect
2024-01-17T17:02:34.2059835Z ##[debug]Fetching JSON web token
2024-01-17T17:02:34.2061755Z ##[debug]ID token url is https://pipelinesghubeus26.actions.githubusercontent.com/k75H1DBAfn7O6Mo0TRQmb014cDWVwCbkrZ6RY4JoockeD1mW9W/00000000-0000-0000-0000-000000000000/_apis/distributedtask/hubs/Actions/plans/a5b3151a-44ff-4c0a-bb81-7544446f9994/jobs/6604c111-019b-5ed5-ae03-3fa9f8925512/idtoken?api-version=2.0
2024-01-17T17:02:34.3042451Z ::add-mask::***
2024-01-17T17:02:34.3045055Z ##[debug]Exchanging JSON web token with an access token
2024-01-17T17:02:34.3070577Z ##[error]Exchanging JSON web token with an access token failed: Input required and not supplied: oidc-provider-name
2024-01-17T17:02:34.3071739Z ::endgroup::
2024-01-17T17:02:34.3072010Z ##[endgroup]
2024-01-17T17:02:34.3123024Z ##[debug]Node Action run completed with exit code 1
2024-01-17T17:02:34.3125937Z ##[debug]JFROG_CLI_ENV_EXCLUDE='password;secret;key;token;auth;JF_ARTIFACTORY_;JF_ENV_;JF_URL;JF_USER;JF_PASSWORD;JF_ACCESS_TOKEN'
2024-01-17T17:02:34.3126916Z ##[debug]JFROG_CLI_OFFER_CONFIG='false'
2024-01-17T17:02:34.3127418Z ##[debug]JFROG_CLI_BUILD_NAME='goldenfrog-demo'
2024-01-17T17:02:34.3127921Z ##[debug]JFROG_CLI_BUILD_NUMBER='50'
2024-01-17T17:02:34.3128783Z ##[debug]JFROG_CLI_BUILD_URL='***********'
2024-01-17T17:02:34.3130110Z ##[debug]JFROG_CLI_USER_AGENT='setup-jfrog-cli-github-action/3.5.0'

Reproduction steps

setup jfrog cli using setup action v3.5.0

Expected behavior

no error

Setup JFrog CLI version

3.5.0

JFrog CLI version

2.52.9

Workflow operating system type and version

linux, ubuntu

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

jfrog commad stuck at configuration and failing

Describe the bug

jfrog commad stuck at configuration and failing

Current behavior

C:\actions-runner_work_tool\jf.exe\2.24.2\x64\jf.exe config add setup-jfrog-cli-server --url https://mycompamny.jfrog.io/ --user *** --password ***
25l
Use the arrow keys to navigate: ↓ ↑ → ←

Select 'Save and continue' or modify any of the URLs

🐸 Save and continue

Reproduction steps

intial configure step itself failing, it iused to work before

Expected behavior

should configure without any prompts

Setup JFrog CLI version

JFrog CLI version

Workflow operating system type and version

windows

JFrog Artifactory version (if relevant)

JFrog Xray version (if relevant)

407 http error behind a proxy with no authentication

Describe the bug
The action fails to download the cli bin when running behind a proxy that uses no authentication.

> Setup JFrog CLI
  tunneling socket could not be established, statusCode=407
  Waiting 16 seconds before trying again
  tunneling socket could not be established, statusCode=407
  Waiting 15 seconds before trying again
  Error: tunneling socket could not be established, statusCode=407

To Reproduce
Try to run the action on a self hosted runner that's behind the proxy. Workflow used:

      - uses: jfrog/setup-jfrog-cli@v1
        env:
          JF_ARTIFACTORY_1: ${{ secrets.AF_SERVER_CONFIG }}
          http_proxy: "<proxy>"
          https_proxy: "<proxy>"
          no_proxy: "<no proxy>"

Expected behavior
The action should download the bin.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions

Setup JFrog CLI version: 1
Workflow operating system: Ubuntu 20.04
JFrog CLI version: latest? not specified
Artifactory Version: Artifactory Enterprise 6.16.0 rev 61600900

Task leaks credentials to other jobs

Describe the bug
This tasks configured jfrog, but never cleans up credentials after the job is finished. This results in credentials leaking to other workflows that are running on the same GitHub runner if they share the homedirectory, which is a common (required?) configuration for runners in GitHub Enterprise environments.

To Reproduce

Create a workflow that uses jfrog/setup-cfrog-cli@v1
Run the workflow
See that ~/.jfrog/jfrog-cli.conf.v4 still exists after the job has finished, or already exists when you run the same job again.

Please note that this is not reproducible on github.com, since they reset the homedirectory for every job.

Expected behavior

I expect the action to have a post script that removes all jfrog credentials

Versions

Setup JFrog CLI version: current master
Workflow operating system: Ubuntu
JFrog CLI version: 1.44
Artifactory Version: all

What type of repository should I setup in Artifactory to use this action?

Set User-Agent header to setup-jfrog-cli-github-action/VERSION

Currently, the User-Agent header sent is by this action is JFrog CLI's default User-Agent value.
I suggest using setup-jfrog-cli-github-action/VERSION so that requests going out from this action can be identified.

Print error message if no rt server was found

Is your feature request related to a problem? Please describe.
Today, if no secret with the desired prefix is found, no informative message is printed.
Which will probably led to the following message to be printed by the JFrog CLI commands:

Error: the --url option is mandatory

Describe the solution you'd like to see
Add check for existing rt server, and print an informative error message in case no matching secret was found.

Provide the token as output of OIDC authentication

Is your feature request related to a problem? Please describe.

First of all thank you very much for the OIDC integration. It's really great and we can finally sleep at night as we don't have to worry about access token rotation and misuse. That's awesome 🎉

We're already using it in production but as we roll out the feature to more and more teams we're also seeing the first issues. It works really fine for Docker, e.g.

    - name: Use JFrog cli via actions
      uses: jfrog/setup-jfrog-cli@v3
      with:
        version: latest
        oidc-provider-name: devops
        oidc-audience: ...
      env:
        JF_URL: ...

    - name: Ping the JFrog server
      run: jf rt ping

    - name: Build Docker image
      run: jf docker build -t ...

    - name: Scan Docker image
      run: jf docker scan ...

    - name: Push Docker image
      run: jf docker push ...

Now we also want to use it for Terraform. So far our GitHub Action looks like this

      - name: set up terraform
        uses: hashicorp/setup-terraform@v3
        with:
          cli_config_credentials_hostname: ...
          cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}

      - name: terraform fmt
        id: fmt
        run: terraform fmt -check
        continue-on-error: true

      - name: terraform init
        id: init
        run: terraform init

As you can see we're using Access Tokens that we provide as secrets to the workflow. We would like to change that and use the OIDC integration. However we couldn't make it work as we don't have any token :) You're creating the token in the background but you're not providing it to us. We also heard from other teams that they're having problem with Python/Peotry where the tooling needs the token.

Describe the solution you'd like to see

Provide the access token as an output of the setup-jfrog-cli action. Before we started your latest version we've created our own composite action that looked similar to this.

name: JFrog OIDC Action
description: Composite GitHub Action handling JFrog OpenID Connect

outputs:
  token:
    description: JFrog Artifactory Access Token
    value: ${{ steps.token.outputs.token }}

runs:
  using: composite
  steps:
    - name: Get id token
      shell: bash
      run: |
        ID_TOKEN=$(curl --silent \
          --header "Authorization: Bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" \
          "${ACTIONS_ID_TOKEN_REQUEST_URL}&audience=jfrog-github" | jq --raw-output .value)
        echo "ID_TOKEN=${ID_TOKEN}" >> $GITHUB_ENV

    - name: Exchange token with access
      shell: bash
      id: token
      env:
        ID_TOKEN: ${{ env.ID_TOKEN }}
      run: |
        ACCESS_TOKEN=$(curl --silent \
          --request POST "https://.../access/api/v1/oidc/token" \
          --header "Content-type: application/json" \
          --data "{\"grant_type\": \"urn:ietf:params:oauth:grant-type:token-exchange\", \"subject_token_type\":\"urn:ietf:params:oauth:token-type:id_token\", \"subject_token\": \"$ID_TOKEN\", \"provider_name\": \"awesome-repo\"}" | jq --raw-output .access_token)
        echo "token=${ACCESS_TOKEN}" >> $GITHUB_OUTPUT

This action provides the token as an output and our internal teams were able to use it similar like this.

name: build

jobs:
  build:

    runs-on: ubuntu-latest

    environment: jfrog

    steps:
    - name: Get JFrog access token
      id: token
      uses: .../jfrog-oidc-action@main

    - name: debug
      run: echo token ${{ steps.token.outputs.token }}

Describe alternatives you've considered

No response

Additional context

No response

Response status code does not indicate success: 500 Internal Server error

Hello,

Our CIs started to fail yesterday when trying to restore nuget packages. Problem seems to be limited to Github actions only because we were able to restore packages on a local machine using JFrog CLI.

"Response status code does not indicate success: 500 (Internal Server Error)."

Is it related to the recent Github action update to 2.3.0?

Versions

Setup JFrog CLI version: V2
Workflow operating system: ubuntu-latest
JFrog CLI version: latest
Artifactory Version: 7.36.4

Upgrade to Node.js 20 LTS

Is your feature request related to a problem? Please describe.

I'm getting this warning:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: jfrog/setup-jfrog-cli@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Describe the solution you'd like to see

Upgrade to Node.js 20. Create new major version release to keep v3 compatible with Node.js 16.

Describe alternatives you've considered

None

Additional context

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

jfrog/setup-jfrog-cli@v2 breaking change in move from node12 to node16

Describe the bug
Attempting to use jfrog/setup-jfrog-cli@v2 with Github Enterprise Server 3.3.x results in an error Parameter ''using: node16' is not supported, use 'docker' or 'node12' instead.'

Support for node16 wasn't added until GitHub Enterprise 3.4 was released, which happened just a week or two ago. Many environments are still on GHE 3.3.x, only has support for node12 actions.
Thus, the change from node12 to node16 here is a breaking change. If you could please roll back the change for v2, that would be greatly appreciated.
Changing the version of nodejs used by the action is a breaking change for GitHub Enterprise Users. GHE 3.4 with node16

Note: this is the very reason why we saw actions/checkout](https://github.com/actions/checkout) move from rev from v2` to v3!

To Reproduce
Try to use jfrog/setup-jfrog-cli@v2 on GitHub Enterprise Server 3.3.x.

Expected behavior
I expect that I should be able to continue to use jfrog/setup-jfrog-cli@v2 with GitHub Enterprise Server 3.3.x, which supports node12 (not node16)

Screenshots

Versions

Setup JFrog CLI version: jfrog/setup-jfrog-cli@v2
Workflow operating system: linux
JFrog CLI version: latest
Artifactory Version: n/a

Additional context
Add any other context about the problem here.

action not using no_proxy (on windows)

Describe the bug

When running the action on a windows runner (2019) behind a corporate proxy, and pulling with with: download-repository the no_proxy is ignored.

Current behavior

Run actions/jfrog_setup-jfrog-cli@v3
  with:
    download-repository: jfrog_cli_root-remote
    version: 2.35.0
  env:
    JF_URL: ***
    JF_USER: ***
    JF_ACCESS_TOKEN: ***
::group::Setup JFrog CLI
Setup JFrog CLI
  ##[debug]isExplicit: 2.[35](***/sample-pipelines/actions/runs/39980/jobs/159441#step:3:36).0
  ##[debug]explicit? true
  ##[debug]checking cache: C:\actions-runner\_work\_tool\jf.exe\2.35.0\x64
  ##[debug]not found
  ##[debug]isExplicit: 2.35.0
  ##[debug]explicit? true
  ##[debug]checking cache: C:\actions-runner\_work\_tool\jfrog.exe\2.35.0\x64
  ##[debug]not found
  Downloading JFrog CLI from https://***/artifactory/jfrog_cli_root-remote/v2/2.35.0/jfrog-cli-windows-amd64/jfrog.exe
  ##[debug]Downloading https://***/artifactory/jfrog_cli_root-remote/v2/2.35.0/jfrog-cli-windows-amd64/jfrog.exe
  ##[debug]Destination C:\actions-runner\_work\_temp\ee691c3f-b5be-4a67-97d6-c56b[42](https://***/sample-pipelines/actions/runs/39980/jobs/159441#step:3:43)24b26f
  ##[debug]set auth
  tunneling socket could not be established, statusCode=502
  Waiting 10 seconds before trying again
  ##[debug]set auth
  tunneling socket could not be established, statusCode=[50](****=
  Waiting 14 seconds before trying again
  ##[debug]set auth
  Error: tunneling socket could not be established, statusCode=502

Reproduction steps

Setting up a windows runner behind a proxy by specifying .env on host, and specifying the artifactory ulr in no proxy

$env:http_proxy="http://proxy.url:port"
$env:https_proxy="http://proxy.url:port"
$env:no_proxy="localhost;127.0.0.1;<artifactory_url>"
http_proxy="http://proxy.url:port"
https_proxy="http://proxy.url:port"
no_proxy="localhost;127.0.0.1;<artifactory_url>"

Expected behavior

Downloading the jfrog version

Setup JFrog CLI version

JFrog CLI version

2.35.0

Workflow operating system type and version

windows-2019

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

Using jfrog/setup-jfrog-cli with flexible customization in a controlled environment

Is your feature request related to a problem? Please describe.
jfrog/setup-jfrog-cli action supports getting connection details as secrets. However in a controlled corporate environment, users are not capable of generating required json string using provided command. It will be helpful if both remote host/repo/auth can be provide as action inputs.

Describe the solution you'd like to see

- uses: jfrog/setup-jfrog-cli@v2
  env:
    # The JFrog CLI will be downloaded from the configured Artifactory server in JF_ENV_1
    JF_ENV_1: ${{ secrets.JF_SECRET_ENV_1 }}
  with:
    download-repository: jfrog-cli-remote
    download-host: https://[own jfrog host]
   download-auth-access-token: ${{ secrets.JF_ACCESS_TOKEN }}
     or 
   download-auth-basic: ${{ secrets.JF_BASIC_AUTH }}

Additional context
Basic auth and access token are mutually exclusive. Only one is required.

Patch request

Would it be possible to patch this action so that Dependabot does not report any vulnerabilities?
Currently it is finding the following vulnerabilities:

Post https://artifactory..../artifactory/api/search/aql x509: certificate signed by unknown authority.

Hi. We are using Azure DevOps to download our artifacts in a Release Pipeline. So we are using a artifactory service connection in order to download the artifact. But we are facing this certificate issue from a long time. we have tried to provide all type of certs like .crt,.cer, on our agent machine in the folder security/certs. Please provide a solution to this.

Paralell jfrog-setup-cli mess up the jfrog-cli.conf.v6 format

Describe the bug

We have a Github actions self-hosted windows runner box with multiples runners on it. It is common that there are multiple workflows runs running at the same time for runners from these box.

We noticed that if you run multiples workflows runs at the same time that use setup-jfrog-cli action then it can mess up the jfrog-cli.conf.v6 file format and jfrog can't fix it by itself. You need to manually remove it.

BTW: if you use different tokens at the same time for different workflow runs, it could be a problem becaus each one will try to use the same .conf file but need different tokens. But this is not what i described in this ticket.-

Current behavior

'C:\Users\User.jfrog\jfrog-cli.conf.v6' file format is broken
it seems it is using the same jfrog conf file for every run and this is not a good idea if you have multiples runs at the same time, the should be isolated, avoid any file format disruption, etc

Reproduction steps

This can be easily reproduced by using pwsh in the runner box and runs multiples jfrog cli import and clear as it does the setup-conf-cli

current 'C:\Users\User.jfrog\jfrog-cli.conf.v6' content, it looks good, everying works fine. YOu can import a token and then run rt ping, etc

{
  "servers": [],
  "version": "6"
}

PWSH 7: Run multiples request imports and clears in parallel

PS C:\Users\User\Downloads> $Env:JFROG_CLI_LOG_LEVEL="DEBUG"; $Env:JFROG_CLI_OFFER_CONFIG="false"; $Env:CI="true" ; 1..50 | ForEach-Object -Parallel {
     Write-Host
     Write-Host "Step $_"
     & ./jf.exe config import  <token> ;
     &./jf.exe rt ping ;
     & ./jf.exe config  rm --quiet
     }

Step 1

Step 2

Step 3

Step 4

Step 5
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Info] Importing server ID 'jfrog.io'
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Info] Importing server ID 'jfrog.io'
17:45:40 [Info] Importing server ID 'jfrog.io'
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Info] Importing server ID 'jfrog.io'
17:45:40 [Error] the --url option is mandatory
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Info] Importing server ID 'jfrog.io'
17:45:40 [Debug] Usage Report: Sending info...
17:45:40 [Debug] Refreshing token...
17:45:40 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:40 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/security/token
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:40 [Debug] Locking config file to run config Clear command.
17:45:40 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:40 [Debug] Lock hasn't been acquired.
17:45:40 [Debug] JFrog CLI version: 2.55.0
17:45:40 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Usage Report: Sending info...
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:40 [Debug] Usage Report: Sending info...
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Usage Report: Sending info...
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Refresh token failed: server response: 401
{
  "error": "invalid_grant",
  "error_description": "Invalid access token or refresh token"
}
17:45:41 [Debug] Trying to create new tokens...
17:45:41 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/security/token
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] New token created successfully.
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19228.1712591140964825200
17:45:41 [Debug] Sending HTTP GET request to: https://<myurl>.jfrog.io/artifactory/api/system/ping
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Artifactory response: 200
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.11436.1712591140984350300
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.11436.1712591140984350300
17:45:41 [Debug] Config Clear command completed successfully. config file is released.
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10756.1712591141021311400
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 1) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 2) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 3) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 4) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Info] executor timeout after 3 attempts with 0 milliseconds wait intervals
17:45:41 [Debug] Refresh token failed: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Trying to create new tokens...
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 1) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 2) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 3) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 4) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Info] executor timeout after 3 attempts with 0 milliseconds wait intervals
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10756.1712591141021311400
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.

Step 6
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25508.1712591141021311400
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 1) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 2) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 3) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 4) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Info] executor timeout after 3 attempts with 0 milliseconds wait intervals
17:45:41 [Debug] Refresh token failed: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Trying to create new tokens...
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 1) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 2) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 3) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 4) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Info] executor timeout after 3 attempts with 0 milliseconds wait intervals
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25508.1712591141021311400
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Couldn't get Artifactory version. Error: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.14020.1712591141065726000
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 1) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 2) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 3) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 4) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Info] executor timeout after 3 attempts with 0 milliseconds wait intervals
17:45:41 [Debug] Refresh token failed: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Trying to create new tokens...
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 1) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 2) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 3) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Debug] Sending HTTP POST request to: api/security/token
17:45:41 [Warn] (Attempt 4) - Failure occurred while sending POST request to api/security/token: Post "api/security/token": unsupported protocol scheme ""
17:45:41 [Info] executor timeout after 3 attempts with 0 milliseconds wait intervals
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.14020.1712591141065726000
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Info] Importing server ID 'jfrog.io'
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Usage Report: Sending info...
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19228.1712591141173950800
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/security/token
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Refresh token failed: server response: 401
{
  "error": "invalid_grant",
  "error_description": "Invalid access token or refresh token"
}
17:45:41 [Debug] Trying to create new tokens...
17:45:41 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/security/token
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] New token created successfully.
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19228.1712591141173950800
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Sending HTTP GET request to: https://<myurl>.jfrog.io/artifactory/api/system/version
17:45:41 [Debug] Artifactory response: 200
17:45:41 [Debug] JFrog Artifactory version is: 7.82.2
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/system/usage
OK
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10756.1712591141259019800
17:45:41 [Debug] Fetched new token from config.
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10756.1712591141259019800
17:45:41 [Debug] Sending HTTP GET request to: https://<myurl>.jfrog.io/artifactory/api/system/version
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25508.1712591141292193100
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Fetched new token from config.
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25508.1712591141292193100
17:45:41 [Debug] Sending HTTP GET request to: https://<myurl>.jfrog.io/artifactory/api/system/ping
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Locking config file to run config Clear command.
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Artifactory response: 200
17:45:41 [Debug] JFrog Artifactory version is: 7.82.2
17:45:41 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/system/usage
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.14020.1712591141326502400
17:45:41 [Debug] Fetched new token from config.
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.14020.1712591141326502400
17:45:41 [Debug] Artifactory response: 200
OK
17:45:41 [Debug] Sending HTTP GET request to: https://<myurl>.jfrog.io/artifactory/api/system/version
17:45:41 [Error] Post "api/security/token": unsupported protocol scheme ""

17:45:41 [Debug] Artifactory response: 200
17:45:41 [Debug] JFrog Artifactory version is: 7.82.2
17:45:41 [Debug] Sending HTTP POST request to: https://<myurl>.jfrog.io/artifactory/api/system/usage
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9136.1712591141407175500
17:45:41 [Debug] Fetched new token from config.
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9136.1712591141407175500
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Sending HTTP GET request to: https://<myurl>.jfrog.io/artifactory/api/system/ping
17:45:41 [Debug] Refreshing token...
17:45:41 [Debug] Locking config file to run config Clear command.
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19560.1712591141639801200
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19560.1712591141639801200
17:45:41 [Debug] Config Clear command completed successfully. config file is released.
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Locking config file to run config Clear command.
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Error] Post "api/security/token": unsupported protocol scheme ""

17:45:41 [Debug] Artifactory response: 200

Step 7
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Locking config file to run config Clear command.
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.8080.1712591141746253400
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Info] Importing server ID 'jfrog.io'
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.8080.1712591141746253400
17:45:41 [Debug] Config Clear command completed successfully. config file is released.
17:45:41 [Debug] Lock hasn't been acquired.

Step 8
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Info] Importing server ID 'jfrog.io'
17:45:41 [Error] invalid character 'h' after top-level value
17:45:41 [Debug] Lock hasn't been acquired.
17:45:41 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9136.1712591141749410000
17:45:41 [Error] invalid character 'h' after top-level value
17:45:41 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9136.1712591141749410000
17:45:41 [Debug] Couldn't get Artifactory version. Error: invalid character 'h' after top-level value
OK
17:45:41 [Debug] JFrog CLI version: 2.55.0
17:45:41 [Debug] OS/Arch: windows/amd64
17:45:41 [Debug] Locking config file to run config Clear command.
17:45:41 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:41 [Debug] Lock hasn't been acquired.
17:45:42 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.924.1712591141770197200
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.924.1712591141770197200
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Lock hasn't been acquired.
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value

Step 9
17:45:42 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.15648.1712591141845555400
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.15648.1712591141845555400
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.23568.1712591141996445200
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.23568.1712591141996445200
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Lock hasn't been acquired.
17:45:42 [Error] invalid character 'h' after top-level value

Step 10
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Debug] Lock has been acquired for C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.6788.1712591142047935800
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.6788.1712591142047935800
17:45:42 [Debug] Config Clear command completed successfully. config file is released.

Step 11
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'

Step 12
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.26348.1712591142109584400
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64

Step 13
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.22892.1712591142341370700
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value

Step 14
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.4100.1712591142482907400
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25292.1712591142490299200
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.15016.1712591142493533500
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value

Step 15

Step 16

Step 17
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10768.1712591142625405200
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value

Step 18
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.15772.1712591142767660200
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value

Step 19
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9932.1712591142883303600
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10940.1712591142892920300
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Debug] JFrog CLI version: 2.55.0
17:45:42 [Debug] OS/Arch: windows/amd64
17:45:42 [Info] Importing server ID 'jfrog.io'
17:45:42 [Debug] Locking config file to run config Clear command.
17:45:42 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:42 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.24752.1712591142899590500
17:45:42 [Debug] Config Clear command completed successfully. config file is released.
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value
17:45:42 [Error] invalid character 'h' after top-level value

Step 20
17:45:42 [Error] invalid character 'h' after top-level value

Step 21

Step 22
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.5988.1712591143019821400
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value

Step 23
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19728.1712591143086553700
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value

Step 24
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.26000.1712591143203761900
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.6676.1712591143213710000
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.26416.1712591143218625900
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value

Step 25

Step 26
17:45:43 [Error] invalid character 'h' after top-level value

Step 27
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9856.1712591143386852400
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.22672.1712591143389831800
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Error] invalid character 'h' after top-level value

Step 28

Step 29
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.13328.1712591143487762400
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10080.1712591143518373000
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.13688.1712591143539418500
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Error] invalid character 'h' after top-level value

Step 30
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64

Step 31

17:45:43 [Error] invalid character 'h' after top-level value
Step 32
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.10300.1712591143685803300
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.11724.1712591143714819200
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64

Step 33
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64

Step 34
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.2552.1712591143810115000
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.16840.1712591143876654300
17:45:43 [Debug] Config Clear command completed successfully. config file is released.

Step 35
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] Locking config file to run config Clear command.
17:45:43 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:43 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.17384.1712591143892753400
17:45:43 [Debug] Config Clear command completed successfully. config file is released.
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Debug] JFrog CLI version: 2.55.0
17:45:43 [Debug] OS/Arch: windows/amd64
17:45:43 [Info] Importing server ID 'jfrog.io'
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value
17:45:43 [Error] invalid character 'h' after top-level value

Step 36

Step 37
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.23888.1712591144026377300
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.16320.1712591144039084000
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value

Step 38
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.8180.1712591144129124600
17:45:44 [Debug] Config Clear command completed successfully. config file is released.

Step 39
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value

Step 40
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19716.1712591144230370800
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25272.1712591144265789400
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value

Step 41
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64

Step 42
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.20092.1712591144347007200
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value

Step 43
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.23744.1712591144439307900
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.5628.1712591144450084800
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64

Step 44

Step 45
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25980.1712591144581792300
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.17392.1712591144607048700
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.22780.1712591144620369300
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value

Step 46
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64

Step 47

Step 48
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25036.1712591144731263500
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value

Step 49
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.9608.1712591144815241600
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64

Step 50
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.21712.1712591144928127600
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Info] Importing server ID 'jfrog.io'
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] JFrog CLI version: 2.55.0
17:45:44 [Debug] OS/Arch: windows/amd64
17:45:44 [Debug] Locking config file to run config Clear command.
17:45:44 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:44 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.13172.1712591144938134400
17:45:44 [Debug] Config Clear command completed successfully. config file is released.
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:44 [Error] invalid character 'h' after top-level value
17:45:45 [Debug] JFrog CLI version: 2.55.0
17:45:45 [Debug] OS/Arch: windows/amd64
17:45:45 [Debug] Locking config file to run config Clear command.
17:45:45 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:45 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.19560.1712591145002044900
17:45:45 [Debug] Config Clear command completed successfully. config file is released.
17:45:45 [Debug] JFrog CLI version: 2.55.0
17:45:45 [Debug] OS/Arch: windows/amd64
17:45:45 [Debug] JFrog CLI version: 2.55.0
17:45:45 [Debug] OS/Arch: windows/amd64
17:45:45 [Debug] Locking config file to run config Clear command.
17:45:45 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:45 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.25000.1712591145020289500
17:45:45 [Debug] Config Clear command completed successfully. config file is released.
17:45:45 [Error] invalid character 'h' after top-level value
17:45:45 [Error] invalid character 'h' after top-level value
17:45:45 [Error] invalid character 'h' after top-level value
17:45:45 [Debug] JFrog CLI version: 2.55.0
17:45:45 [Debug] OS/Arch: windows/amd64
17:45:45 [Debug] Locking config file to run config Clear command.
17:45:45 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:45:45 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.21916.1712591145078115600
17:45:45 [Debug] Config Clear command completed successfully. config file is released.
17:45:45 [Error] invalid character 'h' after top-level value

jfrog-cli.conf is broken, current C:\Users\User.jfrog\jfrog-cli.conf.v6

  "servers": [],
  "version": "6"
}https://myurl.jfrog.io/",
      "artifactoryUrl": "https://myurl.jfrog.io/artifactory/",
      "distributionUrl": "https://myurl.jfrog.io/distribution/",
      "xrayUrl": "https://myurl.jfrog.io/xray/",
      "missionControlUrl": "https://myurl.jfrog.io/mc/",
      "pipelinesUrl": "https://myurl.jfrog.io/pipelines/",
      "user": "jf-cli-local",
      "password": "<passwd>",
      "accessToken": "<token>",
      "artifactoryRefreshToken": "<refreshtoken>",
      "tokenRefreshInterval": 60,
      "serverId": "jfrog.io",
      "isDefault": true
    }
  ],
  "version": "6"
}```

trying to manually run rt ping and config clear will failed due .conf wrong format

```PS C:\Users\User\Downloads> .//jf.exe config rm --quiet
17:47:46 [Debug] JFrog CLI version: `2.55.0`
17:47:46 [Debug] OS/Arch: windows/amd64
17:47:46 [Debug] Locking config file to run config Clear command.
17:47:46 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:47:46 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.6780.1712591266401197900
17:47:46 [Debug] Config Clear command completed successfully. config file is released.
17:47:46 [Error] invalid character 'h' after top-level value
PS C:\Users\User\Downloads> .//jf.exe config rm --quiet
17:48:04 [Debug] JFrog CLI version: 2.55.0
17:48:04 [Debug] OS/Arch: windows/amd64
17:48:04 [Debug] Locking config file to run config Clear command.
17:48:04 [Debug] Creating lock in: C:\Users\User\.jfrog\locks\config
17:48:04 [Debug] Releasing lock: C:\Users\User\.jfrog\locks\config\jfrog-cli.conf.lck.18276.1712591284114404500
17:48:04 [Debug] Config Clear command completed successfully. config file is released.

Expected behavior

No response

Setup JFrog CLI version

2.52.9

JFrog CLI version

2.55.0

Workflow operating system type and version

windows , amd64, 2.299.2

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

trying to connect lib- dll files from j frog artifactory

How can we help?

In my cs .project file . they have mentioned path , but now we have moved all files to jfrog artifactory .
how to run this build job in pipeline job

eg
False
..\lib\log4net\log4net.dll

<Reference In

Regarding sunset of bintray

Hello,

This repo calls bintray to download the cli in this file: https://github.com/jfrog/setup-jfrog-cli/blob/master/src/utils.ts

According to this blog entry Bintray goes away soon, right?
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

So my question is:
Will there be an update to this repo to deal with this? Or where is the new recommended location to download the cli if we want to patch this ourselves?

Existing JFROG_CLI_BUILD variables are overwritten

Describe the bug
The action overwrites existing values for JFROG_CLI_BUILD_NAME and JFROG_CLI_BUILD_NUMBER with the workflow name and run number.

To Reproduce

Set JFROG_CLI_BUILD_NAME and JFROG_CLI_BUILD_NUMBER in the env context for a workflow or job.
Use the setup-jfrog-cli action for a job step.
Refer to JFROG_CLI_BUILD_NAME and JFROG_CLI_BUILD_NUMBER in subsequent steps.

Expected behavior
Existing values for JFROG_CLI_BUILD_NAME and JFROG_CLI_BUILD_NUMBER are not overridden.

Versions

Setup JFrog CLI version: 2.1.0
Workflow operating system: ubuntu-latest

Additional context
The docs say these values will be set so this may be intentional, but I would only expect them to be set if there is no existing value. As it is now a job has to set the env to the desired values after the action has run which seems especially cumbersome in a workflow with multiple jobs that use the setup action where you'd expect a single declaration in the workflow env to be sufficient.

Getting 404 while uploading package to JFrog artifactory

While uploading file to JFrog artifactory using Github Action we are getting 404. seems to it's appending "Build" metadata like "Build number, Build name " etc..

Here is the build log(uploading url):
https://artifactory.xyz.com/ext-release-local/xyz-CCPX/demo.env;build.number=33;build.timestamp=1659113030285;vcs.revision=35fdebe46da530800c16b011e2aba1756c2d6d6f;vcs.url=https%3A%2F%2Fgithub.com%2Fxyz-prod%2FCentralised-Config-Files.git;vcs.branch=master;build.name=Upload+Config+files+to+Artifactory:

Here is the workflow

name: Upload Config files to Artifactory

on:
push:
branches:
- master

workflow_dispatch:

jobs:
publish:
runs-on: [self-hosted, linux, X64]
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Setup Artifactory
uses: jfrog/setup-jfrog-cli@v2
- name: Upload to Artifactory
run: jf rt u --spec artifactory-spec.json --url 'https://artifactory.xyz.com' --user ${{ secrets.xyz_ARTIFACTORY_USER }} --password ${{ secrets.XYZ_ARTIFACTORY_PASS }}

Here is the spec file

{
"files": [
{
"pattern": "configs/*.env",
"target": "ext-release-local/xyz-CCPX/"
},
{
"pattern": "configs-tf/tf-apply.sh",
"target": "ext-release-local/xyz-CCPX/TF-CONFIG/"
}
]
}

How can we skip the build metadata during upload, like "build number, buildname" etc..

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.