Refactor: JenkinsServer runs the risk of being a God Class

The JenkinsServer class is pretty large already, and is growing with every new feature.
In the spirit of single-principle responsibility, would it be more scalable going forward grouping related methods i.e. all job accessor/mutators, all view accessor/mutators methods into their own manager classes, meaning that the JenkinServer has methods to retrieve these managers to call existing methods on, rather than calling existing methods directly on the JenkinsServer class?

Beginne damit, die Klasse JenkinsServer zu lesen und ihre Accessor-/Mutator-Methoden für Jobs und Views zu katalogisieren. Ermittle, wie verwandte Methoden in Manager-Klassen gruppiert werden könnten, wobei die bestehenden JenkinsServer-Einstiegspunkte erhalten bleiben; das Issue benennt weder Tests noch eine konkrete Abschlussgrenze.

Vom Indexierungsmodell aus dem Issue-Text verfasst.