So I have come up with a way to do this, but not sure what the best way to implement it. Basically if I save the previous parameters to a file so when the job is re-executed, they are loaded and new variables are updated.
Let's assume I have an environment variable file already saved with parameters from both job A and B (i've included job version numbers): job_a_var1.1 job_a_var2.1 job_b_var1.1 job_b_var2.1 job_b_var3.1 Now let's say job A triggers, the new environment variable file will be: job_a_var1.2 job_a_var2.2 job_b_var1.1 job_b_var2.1 job_b_var3.1 So this way I can have variables persistent. I'll need to probably save and copy the file to the CI server from the nodes. Are there existing ways to do this or will I need to write my own plugin? I would have thought that joining two jobs with parameters would have been easier. Any help would be appreciated. Thanks, 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
