Hi, Long story short: is it possible to have a job which builds another job, in particular a parametrized one?
We have a Cucumber+Selenium project which runs E2E tests against our different test environments. Something pretty standard. For this kind of job, the parametrized build seems to be the best idea. Otherwise we would have to create one job for each test environment. duplicating the job configuration. Then it would be a nightmare to keep all the job configurations in sync, in case we need to change something. But there's a problem with the build history. I want to see a separate build history for each environment. It doesn't make sense to have an interleaved history. It would be messy. So an easy solution could be to have a job which calls the parametrized job passing the actual value for the environment. This way the build histories would be kept separate, and at the same time we would also get to avoid duplication. Is that possible? Or do you have any other idea/solution? Thank you very much. Alberto -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5f64c8d1-db57-4002-9aa7-5e574638b76c%40googlegroups.com.
