What you are looking for is https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin The downside is that it does not use the build in downstream and upstream relationship between jobs and some plugin may not work properly. The upside is that it is the best plugin to orchestrate build flows. Unfortunately when it comes to build pipelines there is no magic plugin in Jenkins, there are always drawbacks and for now all attempts are more work arounds than true solutions for handling build pipelines.
Le vendredi 29 mars 2013 13:03:30 UTC-4, Marc Esher a écrit : > > Greetings all, > > I have a number of standalone jobs in Jenkins... build/compile, artifact > generation, test runs, webserver restarts, CDN cache invalidation, and so > forth. > > What's the preferred approach for Assembling steps into a Build Pipeline > without adding upstream / downstream dependencies into these standalone > jobs? > > Ideally, I'd have something like this: > > Pipline Step 1 Job > Runs Standalone Step 1 Job > Kicks off Pipline Step 2 Job > > Pipeline Step 2 Job > Runs Standalone Step 2 Job > Kicks off Pipeline Step 3 Job > > ... and so forth. > > Such that Each pipeline step is essentially just a workflow configuration > step that orchestrates other standalone jobs and then, upon successful > completion of those standalone jobs, invokes the next step in the pipeline. > I really don't want to add upstream/downstream dependencies into those > standalone jobs, and I don't want to create duplicates of those jobs whose > only difference is the addition of dependencies. > > Thanks for guidance, > > Marc > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
