Solved this by using the REST API for getting info of the build , specifically the md5:
export MD5BUILD=`curl -X GET -u jenkins:$ARTIFACTORYPASSWORD -H 'Content-Type: application/json' http://artifactory:8081/artifactory/api/build/$ORIG_BUILD_NAME/$ORIG_BUILD_NUMBER | grep sha1 | awk -F"\"" '{print $4}'` And then moving to the libs-release-local with renaming of the artifact curl -X PUT -u jenkins:$ARTIFACTORYPASSWORD -H 'Content-Type: application/json' -d '{ "checksums" : {"sha1" : $MD5BUILD} }' http://artifactory:8081/artifactory/libs-release-local/com/company/Product/Product-$VERSION.$SUBVERSIONUM-RELEASE.bin -- View this message in context: http://forums.jfrog.org/Promoting-to-Release-repo-with-REST-API-tp7579926p7579928.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
