title: Jenkins CI server and Nexus Server on the same Box
body: <p>I am in a situation where I have one Build Server box which is to carry out all continuous integration and manage our maven repository. The box works as follows:</p>
  
  <ol>
  <li>There is one maven repository which is hosted through Apache Server as a URL for developers to use</li>
  <li>All Jenkins jobs (including release jobs) run mvn install so that artifacts are kept in this one repository.</li>
  </ol>
  
  <p>I would like to get rid of the Apache server and run Nexus on this same box to manage and host repositories, however I have the following questions/ideas:</p>
  
  <p>With Nexus and Jenkins on the same box, will it mean that I will have to manage two repositories, one where maven installs an artifact to a local repository, and one where maven deploys an artifact to nexus? Would it be possible to have Nexus manage the "mvn install" repository also? How can I make sure we don't run out of disk space on the server very very quickly all the time?</p>
  
  <p>Thanks</p>
  
  <p>Added as response to comments: Thank you both, I am thinking I will just set the Jenkins jobs and release plugin goals to mvn package deploy:deploy in order to skip the install phase, that way, artifacts go directly from the target directory to Nexus. However I guess the Jenkins job will require a local repository from which to use depedencies which will get copied from Nexus to the maven local repository during the build, I am not sure if this can be avoided though.</p>