This is all related to WireGuard, but it provides a few things:
A wireguard-sandbox-aws target that spins up a machine on AWS and a local CentOS VM that are connected through WireGuard. Pretty much all you can do with this is get each machine to ping each other on their private addresses, but it was useful for debugging issues with the configuration.
A wireguard-sandbox-with-mac-client-aws. As above, but using the macOS slave rather than a Linux slave.
Configures the Mac slave to connect to Jenkins.
The important part of these is obviously the Jenkins setup. You can test it by running make jenkins-environment-aws. At the end of that, you should be able to log into Jenkins and see 4 slaves connected. I've not actually tested running an SCL build end to end on this yet. I'll do that after you've tested this and submit any issues with that as a separate PR.
Hi Stephen/Calum,
This is all related to WireGuard, but it provides a few things:
wireguard-sandbox-awstarget that spins up a machine on AWS and a local CentOS VM that are connected through WireGuard. Pretty much all you can do with this is get each machine to ping each other on their private addresses, but it was useful for debugging issues with the configuration.wireguard-sandbox-with-mac-client-aws. As above, but using the macOS slave rather than a Linux slave.The important part of these is obviously the Jenkins setup. You can test it by running
make jenkins-environment-aws. At the end of that, you should be able to log into Jenkins and see 4 slaves connected. I've not actually tested running an SCL build end to end on this yet. I'll do that after you've tested this and submit any issues with that as a separate PR.Cheers,
Chris