We have a somewhat complicated job that we use to run a series of tests. Rather than copy it and have to make changes to it, we instead have several parameters to the job and use "launch" jobs to specify the parameters, using the parameterized-trigger plugin to launch our main job. We have enabled "execute concurrently" on the main job to prevent long-running performance tests from blocking our faster integration tests. The problem is that the integration tests run several times per-day, but the performance tests might take several hours to run. The parameterized-trigger doesn't give a way to copy artifacts from the downstream job, only from a particular job or from the last successful job. Normally, when the performance tests finish, the last successful job is one of the faster integration testing jobs, so it copies the wrong artifacts. If parameterized-trigger implemented the extension point as Alan Harder pointed out in https://issues.jenkins-ci.org/browse/JENKINS-10861 , we'd be able to just copy from the appropriate job.