On the marketplace-page for the Artifactory Plugin (https://marketplace.atlassian.com/plugins/org.jfrog.bamboo.bamboo-artifactory-plugin) it says that you can upload and download to/from Artifactory with this plugin. However, I can't seem to find the download-functionality. Is there a hidden task for deployment plans which enables artifact download from Artifactory?
I don't know what's your workflow or what output you're expecting. But to download from Artifactory means nothing more than a simple artifact resolution. Once artifacts are on an Artifactory repository you can either resolve them as maven dependencies into your project or in case you want a single artifact (e.g. application packaged as zip or similar) just use the maven-dependenc-plugin, there is a dependency:get goal for this purpose.
Though that would work, it would mean that the Artifactory-plugin doesn't do what it's supposed to do, and I would have to write a custom task for every deployment rather than using the standartized "artifactory download artifact"-task (which unfortunately doesn't exist). So, is it true, that the Artifactory-plugin isn't capable of downloading artifacts from artifactory for deployment-plans?
I too am interested in this capability as we would like to manage the meta-data about the deployment artefacts in Artifactory so that we can co-ordinate the promotion of an artifact through a number of QA activities occuring in different testing environments on its way into a production environment.
The movement of these artifacts from the build server directly into a target environment is handled by Bamboo via the sharing of artifacts between build stages and deployment plans. What is needed is that deployment plans need to have Artifactory pre-conditions attached to them such that they can query the release suitability of a given as-built artifact from property value critieria. Subsequently triggering a deployment based on rule evaluation. For example a deployment rule into a pre-production environment would ensure all integration testing and user acceptance testing had been successfully conducted before final performance testing was conducted in a specialised load testing environment. The attributes recording these prerequisites results need to be updated and maintained in Artifactory independently of the Bamboo build server.
In terms of the physical location of the artifact it would appear that the deployment of binary artifacts into target environments currently must occur from a Bamboo controlled storage location. What would be ideal is if Bamboo could physically access Artifactory repository co-ordinates via some form of virtual file system interface such that the deployment plans can specifically reference them as files or transfer items. Much in the same way as locally shared artifacts work today.
The plugin is an open-source project from the JFrog guys. You can raise a feature request on https://www.jfrog.com/jira/browse/BAP or even a pull request on GitHub https://github.com/JFrogDev/bamboo-artifactory-plugin.
The Bamboo Artifactory plugin is supposed to do the job of "maven-release-plugin" + Artifactory integration feature in an elegant way. (See https://www.jfrog.com/confluence/display/RTF/Release+Management)
You can have a "Artifactory download artifact"-task either as mentioned above over the maven-dependency-plugin or through the built-in Bamboo Task "Artifact download" if your artifacts are already produced on the Bamboo machine itself (shared plan artifacts).
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs