jfrog / jfrog/setup-jfrog-cli

action not using no_proxy (on windows)

Open
#98 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
266
Forks
110
Avg merge
3d 15h
Merged PRs (30d)
3

Description

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

v3

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by tracing the action's download-repository path and how it handles proxy environment variables on Windows; reproduce with the provided windows-2019 setup. Done means the configured Artifactory URL bypasses the proxy and the requested JFrog CLI version downloads successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.