Skip to content

Conversation

@ehossack
Copy link

This will obviously need tidying to make the process work with the new arm-supporting build, but these were the edits I needed to make to generate a 137 build.

I'm fairly confident in the changes here, but I'm a bit rusty on ansible, so I did rely on AI to help generate some of the code.

@ehossack ehossack mentioned this pull request Jun 12, 2025
This commit introduces a few changes to the playbook
to make recreating the build process on different setups better.
* Debug log at various steps in case credentials expire or
ssh connections timeout
* Creating an internet gateway in accounts which don't have
that
* Being able to run the build process in account with no default
VPC
* Filtering for the latest al2023 AMI if not present
@ehossack ehossack force-pushed the feat/update-ansible-playbook branch from b88d207 to 39d76f6 Compare June 13, 2025 22:06
@Sparticuz
Copy link
Owner

Thanks, I don't think the majority of this is needed, the vpc stuff mostly. But there is some interesting things in this with the 'reconnect to host' stuff. There are many times when ansible has lost connection when gclient is syncing the chromium repo.

@ehossack
Copy link
Author

@Sparticuz without this I couldn't get the compilation play to run in my account. Maybe you have different security settings, but I don't have a default VPC, nor can I create one, so this was all needed to get the complication going.
And in general it's best practice to have a dedicated VPC for one use-case? Along the lines of least privelaged access, in case there are other services running in the same VPC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants