CODEWITHSUNDEEP
artifactoryjfrog-cli
red888
red888

Reputation: 31520

Where does the Jfrog cli store build info and how can I view it and clear it before publishing?

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?

Upvotes: 2

Views: 5117

Answers (2)

yahavi
yahavi

Reputation: 6033

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

To clean local build info files, run the build-clean command:

jf rt bc [build-name] [build-number]

Notice - if you're using a project, please add --project to 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=DEBUG environment 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):

08:26:43 [Debug] Saving build general details at: /var/folders/dn/3smrq2yj2qddjccqlky47mpw0000gq/T/jfrog/builds/85b1af1d96d3418a8940f4a586f4efc0ac143c714b149f3423611057af028ce5/partials

For more information:

Upvotes: 4

vijay v
vijay v

Reputation: 2076

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.

jf rt bp [build-name] [build-number] --dry-run

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.

Upvotes: 0

Related Questions