-
Improvement
-
Resolution: Fixed
-
Major
-
None
Testing DSL scripts before activating them in a production Jenkins environment is good, as documented here https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves
It would be great if there was a more user-friendly and less fragile way than the current method, which only works well for trivially small DSL scripts. Attempting to test real production scripts, eg where several Groovy files are involved across directories, immediately surfaces various directory/package problems for resolving external scripts/classes from the root DSL script. (Some of these problems may be issues with Groovy's underlying class loader, which is fairly strict compared to other scripting languages). This makes it difficult to test complex setups before checking them into production.