title: Job inheritance in Jenkins jobs
body: <p>How do you handle mapping Jenkins jobs to your build process, and have you been able to build in cascading configurations on inheritance?</p>
  
  <p>For any given build I'll have at least three jobs (standard continuous integration/nightly, security scan, coverage) and then some downstream integration testing jobs. The configuration slicer plugin handles some aspects cross jobs but each jobs is still very much its own individual entity with no relationship to the other jobs in its group.</p>
  
  <p>I recently saw QuickBuild and it has job inheritance where a parent jobs can define a standard group of steps and its children can override and specialize. With Jenkins, I have copies of jobs, which is fine until I need to change something. With QuickBuild the relationship between jobs allows me to spread my changes with little effort.</p>
  
  <p>I've been trying to figure out how to handle this in Jenkins. I could use the parameterized build trigger plugin to allow jobs to call others and override aspects. I'd then harvest the data from the called jobs to its caller. I suspect I'll run into a series of problems where there are aspects which I can't override which will force me to implement Jenkins functionality in my own script thus making Jenkins less useful.</p>
  
  <p>How do you handle complexity in your build jobs in Jenkins? Have you heard of any serious problems with QuickBuild?</p>