Jenkins as a Netkan "source"

[HebaruSan]

Background

The Netkan transformers for GitHub, SpaceDock, and Curse are implemented as "sources":

• an interface defining an API
• a class implementing that interface
• classes defining objects returned by the API

See https://github.com/KSP-CKAN/CKAN/tree/master/Netkan/Sources

This provides a common, test-friendly structure for these $krefs.

Motivation

Currently Jenkins, the $kref method for all of (and only) @sarbian's mods, doesn't work this way.

• It's a single monolithic class with all of the logic in the Transform method
• It has no tests

It also makes twice as many calls to the server as strictly necessary: one to get overall info about the job, and one to get the latest build using its build number.

Changes

Now Jenkins is implemented as a source like the others.

Now there are tests for Jenkins!

Now we get the latest build in one step using the URL for that:

• https://ksp.sarbian.com/jenkins/job/ModuleManager/lastStableBuild/api/json
• https://wiki.jenkins.io/display/JENKINS/Remote+access+API