Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds support for the Job DSL plugin's approach to automatically configure jobs
When the Jenkins master is started now a
seed-job
automagically appears, runs, then creates several additional jobs that in turn also start running not long after (may want to enter shutdown mode to just observe them queuing up)The seed job does actually fail then, as the 5th example demonstrates how to include external code which a later Script Security plugin integration seems to have broken. There's even an outright option to disable it for Job DSL in the config but it doesn't seem to work ...
The DSL has nice formatting in IntelliJ at least, although exactly how far it goes is up for debate. Syntax highlighting for everything else isn't always working, the
DslScriptLoader
class in an init script doesn't connect right yet IntelliJ knows what it is.Why did you take this approach?
MOAR AUTOMATION!
Contribution checklist
A picture of a cute animal (optional)