I opened an SO post (that no one seems to be interested in)
https://stackoverflow.com/questions/59314501/jenkins-job-dsl-some-way-to-do-a-dry-run
I use the jenkins job dsl to create my multibranch pipeline jobs. It works
great with one glaring issue- safely confirming changes _before_ applying
them.
A tool like terraform presents the ideal workflow for this- run "plan"
_first_ and see what is going to happen, then run "apply" and make those
changes
There is currently no built-in way to do this but are there at least any
hacky workarounds? For example is there any way I can wrap the
multibranchPipelineJob('example'){} closure or extend it in some way where
I could have it output what changes its going to make?
What I want is for my seed job to first output what it's going to change
and wait for user input, then if the user confirms make the changes
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c24372bb-f210-4449-8993-691a9bb941dc%40googlegroups.com.
