28 мар. 2022 г. · As @vijay said, to see the build info before publishing, you can use the --dry-run flag: jf rt bp [build-name] [build-number] --dry-run.

25 февр. 2019 г. · You need to publish the build after uploading artifacts, using jfrog rt bp. Read more about build integration here: jfrog.com/confluence/display ...

1 мар. 2024 г. · I am trying to get a better understanding of how to correctly use the Jfrog CLI and Artifactory (AF) to create a build and update it through the project's ...

22 мар. 2022 г. · Inside of a Jenkins pipeline, it's required to use JFrog CLI to publish any kind of artifacts because of the security policies. Is there a way ...

17 окт. 2022 г. · I need to promote these dependencies to test and staging artifactory. How can i do this in jfrog? Whats the expected process for this now? More ...

9 февр. 2023 г. · We are using maven as the build tool, GitHub actions as the build agent, and Jfrog as the artifactory to deploy the jar files. We have both snapshot and ...

11 апр. 2019 г. · Can i use just docker push instead of ./jfrog rt dp . Does it make any difference if i use either of them. What's use of below lines of code. Is ...

22 июл. 2021 г. · Can you please make sure that the build name and number are the same in "build-collect-env" and in the "jfrog rt gradle"? Also please make sure ...

12 нояб. 2020 г. · The JFrog CLI, which you are already using, can be used for collecting build info. You can add artifacts when uploading them in the following ...

20 мар. 2023 г. · A 403 forbidden error indicates that a user that has been configured in JFrog CLI does not have enough permissions to deploy builds.