I am reviving pipeline support for openstack-cloud plugin[1]. I am
somewhat surprised by several things that seems to be common across
multiple pipeline supported plugins:
- The DSL objects are written in groovy _and_ attached as a resource to
be compiled at runtime.
- They are loaded by the classloader of the CpsScript object and not the
one of the plugin that distribute it (which seems to break plugin-first
classloading).
Is that a random maintainer decision or is there some reason behind that
I do not see? (Is that because of CPS and making the DSL methods itself
continuable?) Is that the only limitation I will observe if I provide a
compile-time compiled java class to pipeline instead? What about the
classloader?
[1]
https://github.com/jenkinsci/openstack-cloud-plugin/pull/145/files#r112932744
Thanks, Jesse!
--
oliver
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/82774bb9-dc88-80ae-a18a-f6b9aeb6c1f7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
