I have marked the google docs for all three as being discussed here. We may
have to pull out those proposals if they prove to be problematic.
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?
(b) be limited to features which involve interacting directly with the host
> Jenkins
> service in a way that would be impractical to simulate otherwise.
>
The http request plugin is "untestable" by that definition, yet it is
useful to talk to external services.
Sometimes, it can be useful to talk to a remote Jenkins master from another
Jenkins master.
But 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?
Thanks,
Martin
On Friday, December 28, 2018 at 11:56:05 AM UTC-5, Jesse Glick wrote:
>
> I am afraid my immediate reaction to both this and the Artifactory
> REST plugin proposal is that we would be better off without such
> plugins. As an “emeritus maintainer” of `workflow-cps` I can say that
> this kind of feature is rather risky and prone to weird bugs, and
> would burden efforts to produce an alternate execution engine. Writing
> an external script (in Python or whatever) is much more reliable and
> testable:
>
> withCredentials([string(credentialsId: 'other-jenkins-api-token',
> variable: 'TOKEN')]) {
> sh 'python jenkins-tricks.py'
> }
>
> Pipeline steps should (a) have simple, databinding-compatible input
> types and ideally only primitive/`String` output types; (b) be limited
> to features which involve interacting directly with the host Jenkins
> service in a way that would be impractical to simulate otherwise.
>
--
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/473d352e-4a9d-4f6f-8305-10ecd96f507d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
