AWS-hosted runners

[sdarwin]

There are multiple ways to add AWS-hosted runners to boostorg/boost-ci.

1. Update .github/workflows/ci.yml so that it uses the new runners instead of GitHub runners.

or

2. Add another file .github/workflows/ci-aws-hosted.yml This offers a choice, and doesn't force the new method. In the short term this is probably the way to go, because the upstream terraform project is in flux.

or

3. An open pull request "feat: Adding runner_enable_default_labels variable #3491" in https://github.com/philips-labs/terraform-aws-github-runner should be included in the design, and when it's available that will change the instructions for boost libraries. Therefore, wait before continuing.

In the meantime anyone is welcome to experiment with the self-hosted runners https://github.com/cppalliance/githubactions however the config will need to be modified.

[jeking3]

Can you explain more about the use of AWS-hosted runners? Are we working with AWS to get resources to build? I work at AWS, so if we need to strengthen the relationship, let me know.

[sdarwin]

Can you explain more about the use of AWS-hosted runners?

https://github.com/philips-labs/terraform-aws-github-runner enables AWS-hosted runners. I implemented this and it's used on beast, unordered, url.

Instructions: https://github.com/cppalliance/githubactions

However, before going any further, it will be preferable if the above mentioned pull request 3491 is solved. And then adjust runner labels.

I might work on that myself and send them another PR.

If regular GHA hosted runners are consistently slow, it could be interesting to use AWS.

If regular GHA hosted runners are available, self-hosted AWS runners represent a large expense without much advantage. So, it's not definitely a "win". But something to explore.

[jeking3]

Okay, I might need some data from you at some point about what the load is, but I'll go talk to some folks to see how AWS can help serve this community better.