-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
As per https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/job-dsl-plugin/UHKrv2umo20/JqH0ELbYBgAJ, it would be really useful to have the option to continue processing job DSLs even if an error occurs in one of the groovy files, marking the build as unstable/failed of course.
One good use case for this is that various organizations are using Job DSL to scan repositories and automatically find ones with groovy files (similar to Jenkinsfile) and create jobs for them, however it would be awesome if a groovy failure in one repository did not cause the rest to fail and stop generating, but only affected that team that has the syntax error.
This conceptually difficult. Depending on the setting for "Action for removed jobs", Job DSL will disable or remove any job that has not been generated. So if a script should generate job A and B, but fails to generate B, Job DSL can't decide if job B has not been generated on purpose (and should be disabled or deleted) or if it has not been generated due to an error (and should not be disabled or deleted).