title: Can one Jenkins job handle two types of builds?
body: <p>Currently my team is using Jenkins to do automated builds that are triggered by SVN changes.</p>
  
  <p>Recently, we decided we wanted to use Sonar. We don't want to have the sonar/hudson integration occur for every single snapshot build. We just want it once a week or so. </p>
  
  <p>Our team uses <code>clean deploy -U</code> instead of <code>clean deploy site-deploy -U</code> so simply using the periodical build to trigger sonar won't be enough because it won't have the site information from the build (such as the clover report).</p>
  
  <p>My question is, in one job, is it possible to associate a different goal to different build times? I'm probably not being terribly clear. Can I associate a <code>clean deploy -U</code> to the build triggered by the SVN change but associate a 'clean deploy site-deploy -U' to a build triggered by the periodical build?</p>
  
  <p>Are my only choices to </p>
  
  <p><strong>1.</strong> Convince everyone to have the site-deploy with every snapshot build (thus taking more time) </p>
  
  <p>OR</p>
  
  <p><strong>2.</strong> Create a new job for the weekly build?</p>