Introduce (additional) puppet only Jenkins job

[pcfe]

As a user I want to easily use Option 2: Using a Content View as a Puppet Environment directly from A separate lifecycle for Puppet modules in Satellite 6 by @wzzrd

The idea is that there are 2 HG
a) one for full SOE CI runs
b) one for puppet only

Jenkins should build the job for full SOE CI runs once or twice day for the HG members of a) (so build by schedule)
and do a puppet run on the HG members of b) as soon as there is a git commit (so poll git every minute).

[pcfe]

It is planned (subject to discussion) that both HG share

• a LCE (this is not mandatory, but for different LCE I'd introduce another Jenkins job and maybe braches
• a (C)CV containing all the software needed for testing both puppet only and a full CI run
• one (or more) CG to pull in the puppet modules under test
• a puppet only Puppet Environment

Comments expected and welcome

[pcfe]

This is being worked on in the branch feat-puppet-only

work done so far
5266e37
74ca304
e134fe6
fafc741
23df4e4
9148467
cb38bc5
9bf8a6b
e929214
b8cfea0
5bd61ed
1297df0
537782f

TODO:

• the conditional build flag for the puppet only workflow job definition should probably be renamed to avoid confusion with the forced rebuild flag in the full CI run job definition
• full builds of the members of b) to be triggered via satellite for now, this will get better after the above is changed

[nstrug]

#73 needs rebasing.