title: Should Artifactory NOT be used to capture the build artifacts that Jenkins produces?
body: <p>We use Jenkins to run continuous integration builds. The output of these builds might be an EAR file, a WAR file, or a collection of files that are TAR'd up that get deployed to an upstream environment.</p>
  
  <p>To this point we have used Jenkins to manage the produced artifacts. However, we have Artifactory deployed in-house. Would it be a bad idea to leverage Artifactory to capture the produced artifacts? If so, why? e.g is Artifactory only 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?</p>