-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
add Jenkins metadata to GCE VMs #39
Labels
Comments
This is a cool idea that will help a lot with cleanup |
I think we may have finished this? I believe multiple PRs have gone in related to this. What kind of VMs are you talking about? e2e? Node e2e? |
AFAIK still not done. This is referring to the VMs that are spawned by tests, both for e2e and node e2e - right now I don't think you can clearly tell what build job created them. |
foxish
pushed a commit
to foxish/test-infra
that referenced
this issue
Jan 21, 2017
mungegithub: sizer: Skip generated files
simonswine
pushed a commit
to simonswine/test-infra
that referenced
this issue
Nov 13, 2017
Pass through /var/lib/libvirt directory
ostromart
pushed a commit
to ostromart/test-infra
that referenced
this issue
Jul 26, 2019
mkumatag
pushed a commit
to mkumatag/test-infra
that referenced
this issue
Jan 16, 2020
CarlJi
pushed a commit
to CarlJi/test-infra
that referenced
this issue
Sep 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to clean up old VMs or other resources, I'm often left wondering "where did this even come from?".
We could probably add metadata describing the Jenkins job and build number that spawned the VM, as well as the PR# on PR Jenkins. There's even an
add-instance-metadata
function incluster/gce/util.sh
we can use.The text was updated successfully, but these errors were encountered: