I'm in the same boat. The definition of a pipeline is based on upstream/downstream dependencies: "In order to better support this process, we have developed the Build Pipeline Plugin. This gives the ability to form a chain of jobs based on their upstream\downstream dependencies. Downstream jobs may, as per the default behaviours, be triggered automatically ,or by a suitable authorised user manually triggering it." (from the jenkins plug-in page: https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin)
What I started looking into is first, create a Starter, which I would call with a URL with parameters. For instance: Trigger the STARTER job via URL, like http://jenkins.acme.org/job/parameterized-build/buildWithParameters?VERSION=1.2.3 OR http://jenkins.acme.org/job/parameterized-build/buildWithParameters?VERSION=1.2.4 OR http://jenkins.acme.org/job/parameterized-build/buildWithParameters?VERSION=1.2.5 ETC…. The STARTER job would then pass those parameters to the PIPELINE using the "Trigger Parameterized Build on Other Projects" post-build action (plug-in here: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin), which would then kick off the PIPELINE presumably with the parameters that I passed in via URL call. After a few tries initially, this wasn't working for me. The goal is to send unique triggers via URL to a pipeline and have the pipeline build according to the parameters which will be passed job to job to job all the way down the pipeline. That way, I only need on job per "build" and one pipeline, but it hasn't worked for me yet and at the moment, I haven't had time to experiment any further. I just duplicated the jobs, each with unique parameters for now to get past a deadline. If you have any success, please share. I don't know if I'm going the right way about accomplishing this but in theory, it sounds like it's a good plan. Best, Pete On Mar 29, 2013, at 1:03 PM, Marc Esher <marc.es...@gmail.com> wrote: > 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. > > -- 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.
