Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement a second level cache system #127433

Closed
godofredoc opened this issue May 23, 2023 · 2 comments
Closed

Implement a second level cache system #127433

godofredoc opened this issue May 23, 2023 · 2 comments
Assignees
@godofredoc
Labels
team-infra Owned by Infrastructure team
Projects
Engine V2 builders

Comments

@godofredoc
Copy link
Contributor

Swarming caches are ignored in builds created by sub-builds in buildbucket. This became a larger problem after the migration to real builds. After some research we found that we can have deterministic checkouts with less than 1m 30s by using a combination of GCS and CAS.

This also has the additional benefit of allowing the use of secure caches across buildbucket buckets.
@godofredoc godofredoc self-assigned this May 23, 2023
@godofredoc godofredoc added the team-infra Owned by Infrastructure team label May 23, 2023
@godofredoc godofredoc added this to To do in Engine V2 builders via automation May 23, 2023
@godofredoc godofredoc mentioned this issue May 24, 2023
Merged
8 tasks
auto-submit bot pushed a commit to flutter/engine that referenced this issue May 24, 2023
@godofredoc
Add builders for second level cache of builders. (#42271)
1f964fa 
These builders will generate CAS caches to optimize engine checkouts.

Bug: flutter/flutter#127433

[C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
@godofredoc
Copy link
Contributor Author

CLs:

Engine V2 builders automation moved this from To do to Done May 25, 2023
@github-actions
Copy link

github-actions bot commented Jun 8, 2023

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@godofredoc godofredoc

Labels
team-infra Owned by Infrastructure team
Projects
Engine V2 builders
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@godofredoc