Hi Thomas, sure there is. The imagination of yours is more or less the limit of what you can do with Jenkins. Try the parametrized trigger plugin (https://wiki.jenkins-ci.org/ display/JENKINS/Parameterized+Trigger+Plugin) and make your build sensitive to parameters.
It is a bit hard to tell you a solution as we don't your the jobs configuration but I would create each of the jobs once and then decide where to go from here: a - the jobs are quite simple so it is good enough if each single job can call the follow up job b - the jobs are getting quite complex and it is easier to really create duplicate jobs taking the differences into regards c - you make the build steps condition depending on which upstream (previous) job was calling the current job. You would then have to pass a parameter to be able to differ. This can be done on many ways: - scripting conditional build steps is straight forward until you reach a certain complexity in your job setups. - I think I have also seen a plugin that exectues build steps in a conditional style. Nice but not always sufficient. - There should also be a plugin available that lets you configure the jobs order in a matrix... not sure about it. Your question looks like you are about to get acquainted with Jenkins and want to establish an continous integration based on Jenkins, right? A good advice for starters who don't like the hard cookies ;) - Try to keep it simple at start and make thing running. If this requires 15 jobs more or less duplicated .. so what? - Parameters are your best friends. - Take a proper look at all the available plugins. There are so powerful plugins available. There may also already be a "click'n'save" solution available for your ideas so why invent from scratch if you can install and configure ;) - Don't try to put too many feature, functions, build steps , whatever into a single job rather contrary. If you have splitted your job into logical minor steps is it easier to troubleshoot and make sure that small segments work proper. This may also be of help when you want to make jobs more fine grained as you then will have to inmplement new switches and the like. Fixing one single and small configration is easier and less prone to errors than several job setups with a high complexity. It can become a real pain when your build job is bulk. What if something fails? You would by all means have to re-run the entire job. You can set your builds up in a style that allows you to continue your jobs from where you want or at least from close to where you want. Does not sound worth the effort? Well... depends on how agile the development must be and how long a build job takes. You will love a long job chain with small jobs when your software needs upto a week or more to compile but also an 8 hrs jobs is a pain when it has to be restarted while the dead line is closing in ;) AND you will get a sore arm from stressing the mouse wheel to scroll in order to review your configuration X/ - Take a look at your setup when everything is running. You will probably have loads of space for improvements and you could then also join several minor jobs to a bigger one if it makes sense (logical and/ or convenience) and everything is running smooth. Take care Jan On 21 Mrz., 08:18, Thomas Fischl <fischl.tho...@gmail.com> wrote: > Hello, > > I have a question about job dependencies in jenkins. I have around 10 > jobs. This 10 jobs I want to combine to several build pipelines. But I > don't now, how i can realize this build pipelines without duplicating > each job for each pipeline to specify the project up streaming and > down streaming projects. > > For example, I want to realize following build pipelines > > 1.) Fast Build pipeline (Each SVN Commit) Job - Build Project --> Job > - Smoke Test --> Job - Generate Report > > 2.) Daily Build: Job - Daily Trigger --> Job - Build Project --> Job - > Build Setup --> Job - Smoke Test --> Job - Full Test --> Job - Publish > Build > > 3.) Weekly Build: Job - Weekly Trigger --> Job - Build Project --> Job > - Build Setup --> Job - Smoke Test --> Job - Full Test --> Job - Load > Tests --> Job - Publish Build > > Is there any possible ways to realize this build pipelines with > jenkins without duplicating the jobs. Exists a plugin, where i can > specify a job chain or something like this? > > Thanks, > Thomas
