alphagov / ci-puppet

Puppet configuration for the deprecated GOV.UK CI Environment

ci-puppet

This repo is now deprecated

CI and transition logs are now configured through govuk-puppet.

Development Workflow

• Clone this repository
• Run bundle exec librarian-puppet install to gather the external modules
• Run bundle exec rake to run the tests
• Make changes to the repository
• Run bundle exec rake to run the tests
• Run vagrant up to instantiate the machines (requires Vagrant and either VirtualBox or VMWare Fusion)
• Note whether your change was successful
• Make more changes to the repository
• Run bundle exec rake to run the tests
• Run vagrant provision to apply new puppet code to the machines.
• ...
• Profit!

Oracle Java 7 "fun"

The Oracle Java 7 installer needs to be preseeded with the oracle tarball. If jdk-7u9-linux-x64.tar.gz is present in the vendor folder, the vagrant bootstrap script will copy it into the necessary location before provisioning.

Due to Oracle's licence terms we can't commit this tarball to this (public) repository, nor can we make it available at a download URL that we make public, so determining where to download this tarball from is left as an exercise for the reader.

Provisioning a new environment or a new machine

See the ci-deployment repository README for instructions.

ci-puppet's Issues

Oracle Java license agreement prevents Puppet from running cleanly

When bringing up a ci-slave-1 VM to test #52, I found that Puppet couldn't install all dependencies. Elasticsearch seems to depend on Oracle Java, which won't install without its license being accepted, which Puppet wasn't able to do and so left elasticsearch present but missing that dependency. License error:

oracle-license-v1-1 license could not be presented
try 'dpkg-reconfigure debconf' to select a frontend other than noninteractive

It suggested using apt-get -f install to fix the broken dependencies, which I did, and once I'd accepted the license agreement to install Oracle Java, a second Puppet run completed without any errors. Various other packages failed the first time too, presumably for related reasons (collectd, fail2ban, gettext, ruby1.9.1-dev...).

Is this a known issue, or one which has been solved elsewhere?

Use github-oauth 0.14 from public repo

Commit 065b700 vendored a snapshot version of github-oauth plugin on July 5th. The real 0.14 has been released. We should just use that.