build - Job inheritance in Jenkins jobs -


how handle mapping jenkins jobs build process, , have been able build in cascading configurations on inheritance?

for given build i'll have @ least 3 jobs (standard continuous integration/nightly, security scan, coverage) , downstream integration testing jobs. configuration slicer plugin handles aspects cross jobs each jobs still own individual entity no relationship other jobs in group.

i saw quickbuild , has job inheritance parent jobs can define standard group of steps , children can override , specialize. jenkins, have copies of jobs, fine until need change something. quickbuild relationship between jobs allows me spread changes little effort.

i've been trying figure out how handle in jenkins. use parameterized build trigger plugin allow jobs call others , override aspects. i'd harvest data called jobs caller. suspect i'll run series of problems there aspects can't override force me implement jenkins functionality in own script making jenkins less useful.

how handle complexity in build jobs in jenkins? have heard of serious problems quickbuild?

i point out release of plugin team has developed , published under open source. implements full "inheritance between jobs".

here further links might you:


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -