Is there any documentation available, that informs what valid values can be put into the modules[].type field of a build info document? Is this field somehow interpreted server-side and does it have any semantics, or is it simply informative for the user and we can put any string into it?
Next, is there any documentation available, that informs what valid artifact objects are and how to correctly construct them?
For example:
- The
type field seems to be optional.
- Its unclear to me if the
path field needs to include the repository name or if its relative inside a repository. But if its realtive inside a repository, how is the repository determined? How does the build page lookup a given artifact path to a concrete artifact in a repository? Is that based on on the hash (which one sha1, sha256, md5?)?
Unfortunately, the https://jfrog.com/help/r/jfrog-rest-apis/build-upload api is not very helpful to answer these questions.
Is there any documentation available, that informs what valid values can be put into the
modules[].typefield of a build info document? Is this field somehow interpreted server-side and does it have any semantics, or is it simply informative for the user and we can put any string into it?Next, is there any documentation available, that informs what valid artifact objects are and how to correctly construct them?
For example:
typefield seems to be optional.pathfield needs to include the repository name or if its relative inside a repository. But if its realtive inside a repository, how is the repository determined? How does the build page lookup a given artifact path to a concrete artifact in a repository? Is that based on on the hash (which one sha1, sha256, md5?)?Unfortunately, the https://jfrog.com/help/r/jfrog-rest-apis/build-upload api is not very helpful to answer these questions.