title: How to implement continuous deployment with Nexus and Jenkins
body: <p>I'm trying to implement a continuous deployment system and I seem to not be able to find a good answer for our problem.
  We use Jenkins to run a maven build to generate our artifacts and deploy them to Nexus.  I see a few projects that bundle up everything into a single war or tar file, extract one file per request from Nexus by name and deploy it to an application server, but this requires them to know beforehand what versions they have available.
  My project has quite a few jars/wars/binaries among other artifacts, which don't get deployed using an application server.  What we want to do is be able to do is pull any snapshot or release revision of the software out of nexus and either generate an install package or deliver it directly to a remote server.</p>
  
  <p>Clarification: I want QA or development to be able to select a version from Jenkins; where Jenkins will poll Nexus for the available versions, then perform an automated deploy to a server from Nexus.</p>
  
  <p>Is there an easy nexus/maven way to get software out to a testing system?</p>
  
  <p>So, is there a way to poll nexus to determine what revisions are available through ant/ivy, Jenkins, maven, gradle?  I'll write in something else if it helps.</p>
  
  <p>I see that a similar question was asked here: <a href="https://stackoverflow.com/questions/7737634/how-do-i-choose-an-artifact-from-nexus-in-a-hudson-jenkins-job">How do I choose an artifact from Nexus in a Hudson / Jenkins job?</a>, but it is as of yet unanswered 9 months later.</p>