We are using the Jenkins Build Flow plugin to orchestrate our builds.
Currently, we have worked out a semi-hacky way to dynamically generate a
DSL string based on available jobs and parameters, which we then invoke by
emulating what the plugin does behind the scenes. This woks just fine, but
it's extremely long and complex. Moreover, we want to be able to run this
'DSL generator' from multiple build flow jobs, so we can have
different development branches run by different flows.
In short, we need a way to pull our DSL out into a script file, or better
yet, into the scriptler plugin, then call it from the build flow job. This
will make the jobs much easier to handle, and will
reduce maintenance points. Is there a roadmap for this sort of thing?
Also, one of the big pains of the plugin is that the contents of the text
field in the job are manually concatenated into the flow closure ("flow
{"+dsl+"}") behind the scenes, preventing users from defining functions,
imports, or much of anything. This is part of the reason that our dynamic
build flow generation is so verbose and hacky; everything is being placed
in the flow closure, so anything too robust produces groovy syntax errors.
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
