You can write a Jenkinsfile that creates a clone of any git repository (calling out to Git with sh step for example), hence Jenkinsfiles can be central for however many repositories you have. No need for 100's of copies of the same Jenkinsfile in 100's of git repositories. You can create and manipulate Jenkins Jobs using the REST API from a loop on the command line. For Java projects, you can use this nice library called jenkins-rest <https://github.com/cdancy/jenkins-rest> to talk to the Jenkins REST endpoints. If your devops is python/curl based or other, see Remote access API <https://wiki.jenkins.io/display/JENKINS/Remote+access+API>.
-- 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/f01ab29f-4ae5-4ba9-beb9-4744ac16d82d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.