Jfrog Cli Store构建信息在哪里，在发布之前如何查看并清理信息？
我正在查看有关如何使用 cli 发布构建信息的文档。真正不清楚的是 cli 在运行后续命令时如何以及在何处存储构建信息。
我可以运行一堆命令来“收集”构建信息： https://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-CollectingBuild-Info
然后我运行命令将其发布到 jfrog： https://www.jfrog。 com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-PublishingBuild-Info
其中rt build-add-git 和 rt build-collect-env 之类的命令是否存储 rt build-publish 推送到 jfrog 的构建信息？在磁盘上？
与 rt show-collected-build-info 命令等效的位置在哪里，以便我可以在发布之前查看此信息到底是什么？
如果我需要清除并重新收集它，“刷新”收集的构建信息的命令在哪里？
I'm looking at the documentation for how to publish build info with the cli. What is really unclear is how and where the cli stores the build info when running subsequent commands.
I can run a bunch of commands to "collect" build info:
https://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-CollectingBuild-Info
And then I run a command to publish it to jfrog:
https://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-PublishingBuild-Info
Where do commands like rt build-add-git and rt build-collect-env store build info that rt build-publish pushes to jfrog? On disk?
Where is the equivalent of a rt show-collected-build-info command so I can see what the heck this info is before I publish it?
Where is the command to "flush" the collected build info if I need to purge it and re-collect it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
正如 @vijay 所说，要在发布之前查看构建信息，您可以使用 --dry-run 标志：
要清理本地构建信息文件，请运行 build-clean 命令：
注意 - 如果您正在使用项目，请添加
--project到上面的命令。JFrog CLI 将构建信息文件存储在操作系统的临时目录中。有了上述两个命令后，实际上就不需要直接访问文件了。
但是，如果您仍然需要查看这些文件，则可以设置 JFROG_CLI_LOG_LEVEL=DEBUG 环境变量，并在运行添加到构建信息的命令（例如 build-add- git、build-collect-env 等）：
有关详细信息：
As @vijay said, to see the build info before publishing, you can use the --dry-run flag:
To clean local build info files, run the build-clean command:
Notice - if you're using a project, please add
--projectto the commands above.The JFrog CLI stores the build info files in a temp directory of the operating system. After having the two commands above, one doesn't really need to reach the files directly.
However, if you still need to see the files, you can set the
JFROG_CLI_LOG_LEVEL=DEBUGenvironment variable and look for the following output, after running a command that adds to the build info (like build-add-git, build-collect-env, etc):For more information:
我认为没有刷新命令可以清除它。
您可以运行以下命令来查看未发布的构建信息的构建信息，而无需发布它。
构建信息是构建代理收集的所有信息，其中包括有关构建的详细信息。构建信息包括项目模块、工件、依赖项、环境变量等的列表。
检查以下文件。
哪里是存储在 Artifactory 6.6 及更高版本中的构建信息 JSON。。
新的 artifactory-build-info 存储库以及如何配置其权限。
用于生成构建信息的代码是开放的，并包含在 build-info-go GitHUb 上的项目。构建信息架构可用并作为项目的一部分包含 自述文件页面。
I don't think there is a flush command to purge it.
You can run the below to view the build info of unpublished build info without publishing it.
Build-info is all the information collected by the build agent which includes details about the build. The build-info includes the list of project modules, artifacts, dependencies, environment variables and more.
Check the below documents.
Where is build info JSON stored in Artifactory 6.6 and above..
The New artifactory-build-info Repository and How to Configure Permissions to It.
The code for generating build-info is open and included in the build-info-go project on GitHUb. The build-info schema is available and included as part of projects README page.