The buildfarm deployment uses puppet from the upstream Xenial repositories. As of this writing that's puppet 3.8, which is no longer supported by puppet upstream.
Puppet 4.6 is the oldest release that's still listed on the primary docs site.
Getting running on puppet 4.6+ (and maybe trying to continue to leap to puppet 5.0) will require
auditing the modules we depend on for puppet 4+ support.
When working on #146 I updated every dependency I could to the most recent version that still reported running on puppet 3.
There are an awful lot of deprecation warnings that come from our dependencies right now and it's not currently known whether those features were indeed removed in puppet 4.
.... and probably more. Getting this repository to support puppet 4 and beyond isn't currently on my radar. If there are folks interested in getting it running I'll do my best to provide some amount of guidance, which is why this issue is open.
Known issues with puppet 3 that affect buildfarm_deployment
The buildfarm deployment uses puppet from the upstream Xenial repositories. As of this writing that's puppet 3.8, which is no longer supported by puppet upstream.
Puppet 4.6 is the oldest release that's still listed on the primary docs site.
Getting running on puppet 4.6+ (and maybe trying to continue to leap to puppet 5.0) will require
auditing the modules we depend on for puppet 4+ support.
When working on #146 I updated every dependency I could to the most recent version that still reported running on puppet 3. There are an awful lot of deprecation warnings that come from our dependencies right now and it's not currently known whether those features were indeed removed in puppet 4.
installing puppet 4.x on Ubuntu Xenial
Following this guide will install puppet 4.10.9.
.... and probably more. Getting this repository to support puppet 4 and beyond isn't currently on my radar. If there are folks interested in getting it running I'll do my best to provide some amount of guidance, which is why this issue is open.
Known issues with puppet 3 that affect buildfarm_deployment