I try to keep 1 Jenkins file per folder into the delevery system and it was a pain in the end. I simplify things by moving the Jenkinsfile into a sub repos (we are using Mercurial). So I keep my Jenkinsfile revision outside the main branch and our repos only point to the proper Jenkinsfile sub repos. So a single change to Jenkinsfile can be spread to all project by just updating sub repos version. So we can branch the Jenkins file for each project into the solution individually. It may not apply to your case but may help to consider something like it.
Take care, you will need a up to date Jenkins version to do so, I ran into bugs until really recently to make this work properly. Hope it help, Jerome -- 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/47c3aba5-d8b1-49bd-b81c-045cdcaa4f14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
