jfrog-cli
jfrog-cli copied to clipboard
JFrog CLI is a client that provides a simple interface that automates access to the JFrog products.
- [ ] All [tests](https://github.com/jfrog/jfrog-cli/blob/master/CONTRIBUTING.md#tests) have passed. If this feature is not already covered by the tests, new tests have been added. - [ ] The pull request is targeting...
- [ ] All [tests](https://github.com/jfrog/jfrog-cli/CONTRIBUTING.md#tests) have passed. If this feature is not already covered by the tests, new tests have been added. - [ ] The pull request is targeting...
- [ ] All [tests](https://github.com/jfrog/jfrog-cli/blob/master/CONTRIBUTING.md#tests) have passed. If this feature is not already covered by the tests, new tests have been added. - [ ] The pull request is targeting...
- [ ] All [tests](https://github.com/jfrog/jfrog-cli/blob/master/CONTRIBUTING.md#tests) have passed. If this feature is not already covered by the tests, new tests have been added. - [ ] The pull request is targeting...
- [ ] All [tests](https://github.com/jfrog/jfrog-cli/blob/master/CONTRIBUTING.md#tests) have passed. If this feature is not already covered by the tests, new tests have been added. - [ ] The pull request is targeting...
### Describe the bug Currently when running say `jf atc blabla_generate_error_please` you get this output: ``` $ export CI=true $ jf atc blabla_generate_error_please >file.txt 2>err.txt $ cat file.txt # Nothing...
- [x] All [tests](https://github.com/jfrog/jfrog-cli/blob/master/CONTRIBUTING.md#tests) have passed. If this feature is not already covered by the tests, new tests have been added. - [x] The pull request is targeting the `master`...
Bumps the github-actions group with 2 updates in the / directory: [actions/setup-node](https://github.com/actions/setup-node) and [actions/upload-artifact](https://github.com/actions/upload-artifact). Updates `actions/setup-node` from 5 to 6 Release notes Sourced from actions/setup-node's releases. v6.0.0 What's Changed Breaking...
### Describe the bug Hi, On 25/10/21, we ran the following command successfully: `jf docker scan ${{ parameters.image }} --licenses --format=simple-json > ${{ parameters.outputFolder }}/${{ parameters.reportFilenamePrefix }}.jfrog.json` It worked without...
### Describe the bug According to the [Artifactory documentation](https://jfrog.com/help/r/jfrog-artifactory-documentation/set-the-target-path-for-debian), specifying Debian package properties is done by appending them to the target path when uploading the package. This works when done...