On Monday, December 31, 2018 at 9:34:58 AM UTC-5, Jesse Glick wrote: > > On Fri, Dec 28, 2018 at 5:49 PM martinda <martin....@gmail.com > <javascript:>> wrote: > >> burden efforts to produce an alternate execution engine > > > > The two execution engines I know of are the scripted pipeline and the > descriptive pipeline. Is there talks about a newer one? > > No, that is the same execution engine—`workflow-cps` directly > implements Scripted, and Declarative is a kind of preprocessor for > that. An alternate engine would replace the on-master Groovy > interpreter. >
Sounds like a large complex project. Maybe someone from the Pipeline Authoring SIG could comment? > > > if you say that there are problems with returning non-simple data types, > are you also saying that there are problems providing methods that return > simple data types? > > e.g. jenkinsRest.api().systemApi().version() -> return the version > number as a String? > > The problem here is (1) using the `GlobalVariable` extension point > (please do not), (2) returning intermediate objects with behaviors. > Such idioms rely on particularities of `workflow-cps` (and do not even > work well in Declarative). > Ok, so is there a way forward for plugins of that type (those that intent to wrap REST APIs of external services)? Thanks, Martin -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8f527f86-443a-4980-87b2-524505ac7ed8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
