jfrog / jfrog/jfrog-cli-security
add an option to jf build-scan to not wait for the result
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
The now deprecated jf rt build-scan command did not wait for the scan result to be available when the option --fail=false was used. Thus builds could complete faster if it was sufficient to analyze the result later in Artifactory.
The new jf build-scan seemingly always polls for the scan result until it is available. (Or am I missing something?)
Describe the solution you'd like to see
An option would be helpful to disable the result polling or to set a time limit (without failing the build when --fail=false is set).
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
Locate the jf build-scan implementation and its result-polling path, then compare its behavior with the deprecated jf rt build-scan command when --fail=false is used. Define the option's behavior for disabling or limiting polling, and verify that the build does not fail when --fail=false is set and polling is skipped or reaches its limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100