Hello Francois, I think this -- still rather small amount of additional flexibility -- already asks for scripted pipelines instead of declarative ones (cf. https://issues.jenkins-ci.org/browse/JENKINS-46547).
At least for now, but I guess/assume not just for now… (Although I just stumbled over https://issues.jenkins-ci.org/browse/JENKINS-42224 “Need ability to create reusable chunks of Declarative Pipeline”…) Of course, scripted pipelines within shared pipelines allow for even more fancy and flexible stuff whilst providing the same API for usage in Jenkinsfile, so from the perspective of the users it may not make any difference. Regards, Reinhold P.S.: Nonetheless I therefore hope that (really) all cool features from declarative pipelines will be available to scripted ones too: hm, admittedly at the moment only https://issues.jenkins-ci.org/browse/JENKINS-47286 “Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view” comes to my mind… -- 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/VI1P190MB0255CB3410257449E6D3666AF7AB0%40VI1P190MB0255.EURP190.PROD.OUTLOOK.COM. For more options, visit https://groups.google.com/d/optout.
