Ok, I solved my problem, so here it is for people who are interested. Instead of passing parameters I saved my parameter to property files (one line each key=value) that I archived as artifacts. In job C I retrieved the artifacts from the last successful builds of Jobs A and B and injected environment the variables using the property files. This produced the result I desired. Matt
On Thu, Feb 16, 2012 at 11:32 PM, Matt Fair <[email protected]> wrote: > I have two jobs that I want to manually approve, let's call them Job A > and Job B. Job C is a job that I want to be executed when there is an > approved Job A and B. The scenario is one where I have separate > builds that I to join together to execute a deployment stage. > > Job A has the following parameters that I want to pass to Job C: > job_a_var1 > job_a_var2 > > Job B has the following parameters I want to pass to Job C: > job_b_var1 > job_b_var2 > job_b_var3 > > So when Job C is executed I want it to have the following parameters: > job_a_var1 > job_a_var2 > job_b_var1 > job_b_var2 > job_b_var3 > > If I update the code for Job A and approve it, I want it to use the > new parameters from Job A but the old once I last approved from Job B. > > Using the promotion plugin I have not been able to get the variables > from Job A and B to join properly to be parameters in Job C. It only > uses the newly approved job's parameters. > > So is a scenario like this possible? Any help would be greatly appreciated. > > Thanks, > Matt
