jfrog / jfrog/jfrog-cli-security
jf audit always fails with error
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
I using azure devops extension for jf audit command , when I try to invoke jf audit with directory to pom.xml file
intermittently it works fine . In most of the cases it fails with $HOME not defined error
what is missing here?
/LocalStorage/azagent/_work/_tool/jf/2.44.1/x64/jf audit --server-id="ci-metajob_20230822.1_xray_audit_1692683142231" --fail=true --licenses=true
22:45:43 [Info] JFrog Xray version is: 3.79.11
22:45:43 [Info] Scanning for vulnerable dependencies...
22:45:43 [Info] Detected: maven.
22:45:43 [Error] audit failed while building maven dependency tree:
$HOME is not defined
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the jf audit command against a directory containing pom.xml in the Azure DevOps environment described, checking the intermittent Maven dependency-tree failure and the "$HOME is not defined" message. Done means the audit completes reliably in that environment without this error, with the reproduction conditions or cause documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100