-
Bug
-
Resolution: Unresolved
-
Minor
-
None
We are slowly rolling out Pipelines (to replace our hundreds of Freestyle jobs). A common mistake of some of our early adopters has been to create a GitHub Organization job, instead of either a Multibranch Pipeline or regular Pipeline. The problem with creating a GO job is that it can potentially (once we achieve a critical mass of Jenkinsfiles checked into our ~1000 repositories in our Github Enterprise organization) of it triggering hundreds of builds. We want to prevent users from being able to do this, by some type of global setting disabling that option (or even better, deinstalling a plugin, but that may not be feasible?)
Also as described here: