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

Create an automated way to clean up swarming bot caches #101710

Closed
keyonghan opened this issue Apr 11, 2022 · 3 comments
Closed

Create an automated way to clean up swarming bot caches #101710

keyonghan opened this issue Apr 11, 2022 · 3 comments
Labels
from: postmortem Issues identified as part of a postmortem P2 Important issues not at the top of the work list team-infra Owned by Infrastructure team

Comments

@keyonghan
Copy link
Contributor

It happens caches are polluted between builds on the same bot. Existing way to clean up cache is manually ssh to the bot. This has been an expensive process and it is unreliable and getting more expensive as new security requirements require 2 approvals to ssh the machines.

We should have an automated way to do the clean up.
@keyonghan keyonghan added team-infra Owned by Infrastructure team postmortem labels Apr 11, 2022
@CaseyHillers
Copy link
Contributor

Unassigning myself as I don't have plans to solve this issue. However, I am working on deterministically generating these in #100259 which will make it easier to know the full set of caches bots can have.

@CaseyHillers CaseyHillers removed their assignment Apr 27, 2022
@keyonghan keyonghan added P2 Important issues not at the top of the work list passed secondary triage labels Jul 28, 2022
@keyonghan keyonghan mentioned this issue Aug 30, 2022
Closed
@keyonghan
Copy link
Contributor Author

Closing as obsolete.

@github-actions
Copy link

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 29, 2023
@flutter-triage-bot flutter-triage-bot bot added the from: postmortem Issues identified as part of a postmortem label Jul 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
from: postmortem Issues identified as part of a postmortem P2 Important issues not at the top of the work list team-infra Owned by Infrastructure team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CaseyHillers @keyonghan