This is for provisioning the macOS slave. It sets up Java, the AWSCLI, a Jenkins user and a Rust installation. Since we can't spin up this slave like a VM, there's a playbook for 'resetting' the machine, which undoes those things.
I also updated the manual instructions for setting up the slave. On Mojave it wouldn't let the jenkins user SSH in without disabling PAM authentication for sshd. We need to give the qamaidsafe user passwordless sudo access for use with Ansible, so I added this too.
You could test this by spinning up Jenkins and making sure a build runs through. As per the last time though, it will take a long time because the Windows machine will need to build from scratch. The macOS build will be fast because I've already ran a build on it and it's a static machine. If you really wanted to you could run the reset playbook with make clean-rust_slave-osx-mojave-x86_64, run make provision-rust_slave-osx-mojave-x86_64, then spin up Jenkins and run the build.
Hi Stephen/Calum,
This is for provisioning the macOS slave. It sets up Java, the AWSCLI, a Jenkins user and a Rust installation. Since we can't spin up this slave like a VM, there's a playbook for 'resetting' the machine, which undoes those things.
I also updated the manual instructions for setting up the slave. On Mojave it wouldn't let the
jenkinsuser SSH in without disabling PAM authentication forsshd. We need to give theqamaidsafeuser passwordless sudo access for use with Ansible, so I added this too.You could test this by spinning up Jenkins and making sure a build runs through. As per the last time though, it will take a long time because the Windows machine will need to build from scratch. The macOS build will be fast because I've already ran a build on it and it's a static machine. If you really wanted to you could run the reset playbook with
make clean-rust_slave-osx-mojave-x86_64, runmake provision-rust_slave-osx-mojave-x86_64, then spin up Jenkins and run the build.Cheers,
Chris