Thanks for the quick reply - that's an intriguing proposition! Do you know if all builds from each PR go to the same job that is created in the build-a-job step?
On Wednesday, December 13, 2017 at 2:10:45 PM UTC-8, Victor Martinez wrote: > > if the old tests will be deprecated and removed sooner than later, cannot > you just use the > https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > step? > > Then, the Jenkinsfile will trigger two parallel branches, the first one > about the new tests using whatever is part of the jenkinsfile for running > the new tests, and the second branch will be to trigger another traditional > jenkins job which will run the old test (using the above build step) > > I don't know if it makes sense in your case, but I guess it might simplify > the pipeline tweaking. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/efd618d2-3c61-4a4b-a2de-1f1258a3853f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
