We just took to step to move our CI environment to Jenkins 2. We see that we are creating the same build over and over. The jenkinsfile is great, but now we see that we need to repeat it in every project. At the end that becomes it maintenance nightmare..
We have multiple git projects that are equal in structure and need to be build in the same way. Example: gitrepo - App1 - Jenkinsfile (MultiBranchPipeline) gitrepo - App2 - Jenkinsfile (MultiBranchPipeline) gitrepo - App3 - Jenkinsfile (MultiBranchPipeline) .... We are actually coping the same Jenkinsfile to these projects and if we need a change we need to adapt all of them. So this becomes a nightmare. Is there a better way of organizing this and getting a repeatable way of doing things? - Marco -- 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/ace83cef-7c94-4087-9556-d0f42f38da53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
