we don´t use Jenkinsfile(s) at all - instead we generate all the jobs using the Job-DSL. The jobs than either have the full (generated) code in it - or even better they just call some functions of a shared library. Any modifications can be applied by a new version of the shared library - or by a commit that triggers and updates the JobGen job which will update all jobs.
It´s often a philosophical discussion about pros and cons of Jenkinsfile(s) - for real life projects it has a lot of disadvantages from my point of view. It doesn´t solve your problem - but maybe there´s a way to move towards this approach of managing it? Good luck, Torsten -- 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/0f0c008e-16da-428c-ab27-26ba7280b2e1%40googlegroups.com.
