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 5266e37f8eb8298a1a2ec2d774aa77e094f1d45e 74ca304b7f56a62674d5728066cbd87d1e2bd4b8 e134fe6fe84082876c3f5d7fb5a346c738bdd2e2 fafc741d4c26ddea2958a9d09dfeaa44a2e142c0 23df4e44569796a691bdd376ddea73b686b4891c 9148467b4a664e06ab512a16dc17506f69e463df cb38bc58274a4a1f644f5658b6104ceb1899a17b 9bf8a6b025739251cf98da525810a0772e412da1 e92921479cfc10235e6badded1f981a6f64675eb b8cfea0d316dbaecf3910c3d535660f750254cc6 5bd61edda7eb1ef5bca946cd33c98d262b5eb6c1 1297df091523584c4ebc1a60393fc0adaed624d7 537782f16c58ca32ac4660f8fb7e02bdc54deec5

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.