Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
This is a duplicate of… – noamt Aug 10 '12 at 7:00
up vote 2 down vote accepted

ArtifactoryPro has features for doing what you're asking, so why the heck not? JFrog's documentation even has an example: see

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.