-
Notifications
You must be signed in to change notification settings - Fork 15
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
Setup CI #10
Comments
There's also luci-go but unknown if they're equivalent. Poking around in that I was actually wondering how one caches 33GB worth of chromium ❓ Have you considered contacting GitHub support to see if they have any suggestions? Before I saw this ticket, I was actually going to propose creating a |
I saw that too maybe worth looking into. It appears that they used buildbot before but switched to luci.
Ah I see so brave uses jenkins for their CI. Maybe goma+gha combo could work that would make things simpler.
So goma can be used to off load compilation into cloud servers that's pretty neat. To set this up it seems that we need
I wonder if Github actions could use the goma client to off load builds so we can just setup a goma server/service to get something like CI with GHA hmm.
I will send them an email maybe they know something. |
I was curious how Arch did it, and it seems they don't use gclient et al, but rather Given that the GHA cache is limited to 10G, I was curious if there was a way of converting the tar to a "working" It did get pretty far, so it may be worth exploring how to sideload the llvm-build directory:
where ☝️ is due to |
I also just realized they have chromium GitHub mirror so if GitHub can work with you in some way, they don't need to pay for that clone traffic from GCP; that is, conceptually you just want a pipeline that does Related to that, I would be super curious if the Microsoft/git fork would work in CI. They allege it is for monorepos, which Beacon kind of is given its sibling dependency upon chromium, and that if a build doesn't touch every file the sparse checkout could be a huge win, too |
Just an update: I had a call with EngFlow and their current offering is more suitable for larger teams. They seem to be flexible with their plans so this won't be completely ruled out for now. Buildbuddy said their remote execution API might work with goma so I will check that out. Even if we have a CI just for linux that would be good enough as a start.
I see my understanding is that gclient also pulls those dependencies so perhaps that was the issue. I found a PR that builds Ungoogled chromium using Github actions on macOS which is interesting ungoogled-software/ungoogled-chromium-macos#54 seems to take 11 to 13 hours :-D |
We're gonna need some CI infra to do builds for Beacon this should make things a lot easier. Chromium uses LUCI it's a bit too googly i'm not sure if it's documented well enough to be usable for non-google projects
The text was updated successfully, but these errors were encountered: