chore(ci): github runner for build_all is bumped from macos10.15 to 12

[nstng]

Signed-off-by: Nils Semmelrock nils.semmelrock@tngtech.com

Summary

Context

• github is deprecating macos-10.15 runners. Alternatives are macos-11 and 12 runners.
• This goes along with "brownouts" - one day per week macos-10.15 runners are not usable - see The macOS 10.15 Actions runner image will begin deprecation on 5/31/22 and will be fully unsupported by 12/1/22 for GitHub and ADO actions/runner-images#5583
• Slack discussion: https://magmacore.slack.com/archives/C01MDUQDFC3/p1658411534798269
• We have 4(5) jobs using macos-10.15 runners
  • CWF
  • FED
  • LTE integ tests (make and bazel)
  • build_all
• CWF, FED, LTE are using the traffic server which has a known issue on macos >=11 - see magma_trfserver not starting up correctly on Mac OS #13245
  • here we need the base image bumped to ubuntu 20.04 - this is ongoing (issue link TBD)

Here

• the build_all job is not using the trf server and can be bumped
• we decided to use macos 12 because
  • its more recent
  • it already has vagrant and virtualbox pre-installed - the 11 image does not
• I also took the liberty to add a workflow_dispatch trigger for easy testing
• setup pyenv (gabrielfalcao/pyenv-action, with py 3.8.5) does not work with macos 11/12 - but it seems in a test run that it is not needed ... looks like tech debt -> removed

Test Plan

• real change will only run on master first
• test run on branch (with tweaks to be runable): https://github.com/nstng/magma/actions/runs/2713097965

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

dp-workflow

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 332fad5.

[Neudrino]

setup pyenv (gabrielfalcao/pyenv-action, with py 3.8.5) does not work with macos 11/12 - but it seems in a test run that it is not needed ... looks like tech debt -> removed

Optional idea: If this is tech-depth, should we maybe create a ticket, to remove it from other setups as well?

[nstng]

Optional idea: If this is tech-depth, should we maybe create a ticket, to remove it from other setups as well?

imho an extra issue is not needed as this needs to be done when the other jobs are bumped to macos-12 (and also it will be checked there if the pyenv is needed in those jobs)