-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin GHA runners to ubuntu-24.04 #1853
Conversation
4302971
to
47a4f9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor question about the logging, but otherwise LGTM!
ansible/Makefile
Outdated
@@ -29,7 +29,7 @@ provision-vms: | |||
|
|||
.PHONY: destroy-vms | |||
destroy-vms: | |||
ansible-playbook -i $(CONTEXT) \ | |||
ansible-playbook -i $(CONTEXT) -vvvv \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the purpose of the extra logging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did this because of a weird flake I got, but then the issue never happened again and I forgot to remove the verbosity, I'll roll it back before merging.
Description
Having runners configured to
ubuntu-latest
means that the underlying VM could be updated to a newer version without us knowing. This should only be a problem when a new LTS version of Ubuntu is made the default for GHA and shouldn't be a major problem for us, since we mostly use generic tools pre-installed on all runners but, just in case, we should be explicit about what version of runner we want to use.Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
Run as many workflows as possible and checked none of them is broken.