job-dsl-gradle-example VS jenkins-script-console-scripts

Yeah I've tried with the later approach days ago and make it work today, thanks to this helpful repo: https://github.com/sheehan/job-dsl-gradle-example :D

Have a look at https://github.com/sheehan/job-dsl-gradle-example it's a nice example that even allows you to test your job configuration.

You can capture plugins and Jenkins versions using the script console to provision a second pristine Jenkins for additional testing like upgrade testing. I go deeper into this with complete immutable Jenkins infrastructure with jenkins-bootstrap-shared.

Groovy scripts for Jenkins administration

Based on other comments I recommend: - Committing your Jenkins config to a local git repo so you can see how an upgrade affects it with git diff - Capture you plugin versions with Jenkins version

You can do this by script console yourself and use the community docker image. Alternately, you can try out jenkins-bootstrap-shared project I made which pulls Jenkins into a JKD8 container (I plan to upgrade it to OpenJKD11 since Jenkins now supports that).

Delete builds for branches and tags after 120 days

If you're an admin in Jenkins, then you cam retrieve the credentials via script console. I did a talk which discusses using the script console. You can run this script which exports most common credentials in Jenkins. It will render them as plain text which you may be able to use to log into vault.

Here’s a list of properties I’ve found. https://github.com/samrocketman/jenkins-script-console-scripts/blob/main/aggressive-cloud-provisioning.groovy