Automatically add new manifests to the Jenkins pipeline

[dblock]

Is your feature request related to a problem? Please describe.

In #461 we generate a new manifest. Add it to the build pipeline.

Describe the solution you'd like

Part of the update modify something that adds the version to the build/test pipeline.

[dblock]

@peternied I don't see where I can add/commit configuration that would, for example, add 2.0 builds. Where's the list of the manifests that we're building?

[mch2]

To do this I think we need to set up a job DSL with pipelineJob that kicks off a job using our Jenkinsfile with a manifest as input. Right now the job is created manually that loads the Jenkinsfile from this repo and invokes it with the 1.1 manifest.

[peternied]

We have too many manual processes around the build at the moment, if we enable more than one at a time it is going to bog us me down.

When logs are publicly accessible #453 and the public CI instance is available - I'd be happy to support N manifests build because then the primary bottleneck is removed.

[dblock]

Here's a manual version of what we're trying to automate: #664.

[dblock]

Closed via #1407