You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question regarding the relationship between frontend, scheduler and storage in the kubernetes setup. I am currently using buildbarn as a remote build server for chromium. My main question is with regards to caching. By default if I am sending build requests to the frontend are the actions automatically cached or do I need to tweak the config there? Thanks!
(BTW this is an awesome project Ive been able to get chromium builds down to around 30 minutes)
The text was updated successfully, but these errors were encountered:
The Execute requests are passed through the frontend to the scheduler. The scheduler then pass the request to one bb-worker. When finished, the result is uploaded by the bb-worker to the AC (action cache) and outputs are uploaded to the CAS (content adressable storage), unless ExecuteRequest.do_not_cache=true.
I have a question regarding the relationship between frontend, scheduler and storage in the kubernetes setup. I am currently using buildbarn as a remote build server for chromium. My main question is with regards to caching. By default if I am sending build requests to the frontend are the actions automatically cached or do I need to tweak the config there? Thanks!
(BTW this is an awesome project Ive been able to get chromium builds down to around 30 minutes)
The text was updated successfully, but these errors were encountered: