Artifactory Download Spec File

Bamboo there are 2 separate generic jobs, deploy and resolve, that are used to upload and download files from artifactory using the bamboo artifactory pluginjust as in the previous ci servers, the option to choose either a file or job configuration as a spec source is also available here. Artifactory download spec file. We have a jenkins free style job that with a generic-artifactory integration enabled the download details have is filled with an aql any "correct" aql query cause an npe when job starts.

artifactory download spec file

Hi, i'm using the artifactory plugin with ivy when i create my jar file with ivy it generates a file something like myjar_1234jar with a corresponding ivy file (ivy_1234xml), however when this is uploaded to artifactory using this plugin the jar and ivy files have had their names changed the jar file is now called myjar_1-1234jar (it's got an extra '1-' before the version number. When you're not setting a build number, jenkins tries to first fetch the latest build number from artifactory, for the specified build name. then, it builds an aql query with the build name, build number and the other properties in the file spec. and sends it to artifactory to get the artifacts.. I am encountering a problem on the buildinfo generation (empty or non existent file), all details can be found on the dedicated stackoverflow post). stack: jenkins (up to date), gradle 3.1, artifactory.

visit link reference