A cron job needs to be developed that will take one, or potentially more, repositories and generate the needed jcasc.d/community/*.yaml files that will allow the community to do more self-management of their Jenkins systems.

It will need to use the utility developed in RELENG-3035 for merging files. It will also need to reject creating configuration for select LF (puppet) managed JCasC options. To be smart, it should inspect the yaml files that will live in jcasc.d/ (excluding the community directory) and make the determination of what should not be pulled from the community based on what is being managed by puppet.

The end result of this job will be a set of generated yaml files in the jcasc.d/community directory that is built from the community supplied files. It will upon completion of laying down the files cause Jenkins to reload it's JCasC configuration to apply the updates, but only if files are changed.

We will need to come up with a sane scm polling time for this so that we're not polling all the time, but also not lagging so far behind that upon merge of changes we are waiting a long time for them to be applied.