artifactory - Composing custom builds - JSON payload examples -
are there more examples of custom build json payloads beyond available @ https://www.jfrog.com/confluence/display/rtf/artifactory+rest+api? or perhaps more in-depth documentation on “application/vnd.org.jfrog.build.buildsbyname+json” payload?
we have build produces both jar/ivy , rpm files (and other file types artifactory doesn’t know content of). today, publish generic repository keep together.
what ideal able create own custom build using rest api, composed of jar files + rpm files, can licensing searches across them.
in given example, artifacts composed in build referenced id/name/hash reference.
the problem current jenkins/artifactory/gradle plugin use our build separated amongst many smaller builds, ultimately, released one. makes making full report difficult, , doesn’t have way license checks including rpm files. want able publish 1 build, contains know in build.
the current setup has uploading our jars maven repository, adds time builds, given publishing same content generic repository alongside rpms , other content.
thanks!
the build info json documented in readme of repository: https://github.com/jfrogdev/build-info
which repository holds code of build info engine used various jfrog ci/build plugins. can create own bi json, and, if you're going use java that, should check out project demonstrates usage of various build info java apis:
https://github.com/jfrogdev/project-examples/tree/master/build-info-java-example
another option may want jfrog cli, brought support associating artifact deployment/resolution build object , deploying artifactory. method agnostic file types build produces or build tool using. have @ official documentation here:
lastly, if using jenkins, jenkins artifactory plugin has pipeline apis allow collect artifacts , build information programmatically, , concatenate multiple build info objects deploy them single build entity artifactory, pretty wicked. have read here:
https://wiki.jenkins-ci.org/display/jenkins/artifactory+-+working+with+the+pipeline+jenkins+plugin
Comments
Post a Comment