Artifactory service integration
We support releasing to, and pulling from, Artifactory, and have a technical article outlining how to do this. But some other CI services have plugins or integrations with Artifactory which can be more convenient to use, mainly by raising visibility that the integration is possible and providing steps to use it.
Add a service integration for Artifactory that asks for
- Service integrations are somewhat more limited than variables. We now support group-level variables, so these kinds of integrations can be shared for multiple projects, and we support environment-specific project variables that can be
protected. User may find that using variables is actually more powerful, more convenient, and more secure.
- Do other CI plugins do anything other than provide these variables for use in scripts? From https://wiki.jenkins.io/display/JENKINS/Artifactory+Plugin, it looks like they ask for much the same information, but also provide a "post-build step" which (debatably) makes it easier to configure than working with raw scripts.
External artifact storages (Artifactory, Nexus, etc) are very useful because they store artifacts in ways that end-user tools prefer (APT servers, Docker Hubs, etc). An integrated way to have build artifacts published to external storages would be very nice. Jenkins, Bamboo, and other CI services support this approach.