Could anyone please help to see if there are any potential disadvantages with this approach
In our scenario, where we have multiple projects which get added frequently, we wanted to minimize the effort of creating jobs, so we thought of reusing the jobs with different parameters. And we are using pipelines and parametrized trigger plugins in order to achieve this dependency between the jobs. Here in our case, we have startup, build, test and deploy jobs setup as a pipeline. Startup job is to just accept parameters to trigger the downline jobs such as source code location and common workspace for subsequent jobs. For every new project, we are adding a new startup job with different parameters and triggering the build job which is common for all the projects with parameters being different. Appreciate if anyone can suggest potential disadvantages that we might encounter down the line with this approach. Thanks in advance, Krishna -- 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/34e22d80-b3fd-4308-8631-28960fec1a4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
