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.

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

x/build/internal/gomote: explore destroying the bot after a gomote instance is destroyed #63819

Open
Tracked by #61772
cagedmantis opened this issue Oct 30, 2023 · 0 comments
Assignees
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@cagedmantis
Copy link
Contributor

cagedmantis commented Oct 30, 2023

When a gomote instance runs on a swarming task instead of a bare VM/Container, we should consider destroying the bot after the gomote instance has completed running. This should be an added safeguard for unwanted artifacts being left behind on the instance.

@golang/release

@cagedmantis cagedmantis self-assigned this Oct 30, 2023
@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 30, 2023
@cagedmantis cagedmantis added this to the Unreleased milestone Oct 30, 2023
@cagedmantis cagedmantis added the Builders x/build issues (builders, bots, dashboards) label Oct 30, 2023
@cagedmantis cagedmantis changed the title explore destroying the bot after a gomote instance is destroyed x/build/internal/gomote: explore destroying the bot after a gomote instance is destroyed Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

1 participant