Is it a good practice to capture build artifacts in Artifactory that Jenkins produces?

Question

We use Jenkins to run continuous integration builds. The output of these builds might be EAR files, WAR files, or just a collection of files that are TAR'd up.

To this point we have used Jenkins to manage the produced artifacts.

We have Artifactory deployed in-house. Would it be a bad idea to leverage Artifactory to capture the produced artifacts?

Or is Artifactory meant to hold JARs with versions that can be pulled into projects with Maven when building and not meant to capture artifacts that a continuous integration tool uses?

This is a duplicate of stackoverflow.com/questions/11891890/… — noamt
– noamt, Commented Aug 10, 2012 at 7:00

Matthew Flynn · Accepted Answer · 2012-08-09 21:07:03Z

ArtifactoryPro has features for doing what you're asking, so why the heck not? JFrog's documentation even has an example: see http://wiki.jfrog.org/confluence/display/RTF/Build+Integration

Stack Exchange Network

Is it a good practice to capture build artifacts in Artifactory that Jenkins produces?

1 Answer 1

Hot Network Questions

Is it a good practice to capture build artifacts in Artifactory that Jenkins produces?

1 Answer 1

Related

Hot Network Questions