The BuildFlow DSL for some of my projects has become pretty complex and so
I want to store the meat of the script in an external script. The BuildFlow
DSL would then just be responsible for calling that script and setting up
bindings if necessary.
The advantages of this:
1) For debugging orchestration, I can write functions that simulate what
build() and parallel() do by just printing out the project and parameter
being executed
2) I don't have to worry about using characters that will break the entire
config.xml (<,>,&, etc.)
3) I can edit the script without having to reload jenkins configuration
from disk.
The two open questions I have:
1) Where to store the external script? In the same directory as the
config.xml would be ideal IMO, but how can I can get a reference to this?
Or is there a better place for it?
2) If the bindings for BuildFlow won't be automatically available to the
external script if I call evaluate(new File("path\to\my\script.grooy")),
how can I accomplish this?
Thanks,
Stuart
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
