I've just seen your comment in the open PR regarding https://issues.jenkins-ci.org/browse/JENKINS-27182
> 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 IIUC, you would like to mimic a kind of code review similar to the GitHub Pull Request view process, if so, I'd say you can use the proposal from Daniel Spilker ( https://github.com/jenkinsci/job-dsl-plugin/pull/395#issuecomment-132346716) with https://github.com/jenkinsci/job-dsl-plugin/wiki/Testing-DSL-Scripts and the pipeline to validate it: > 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? https://plugins.jenkins.io/jobConfigHistory might help you My two cents -- 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/21df7215-6481-45bc-b93f-af89a8be163c%40googlegroups.com.
