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

Identify and assign release-blocking job owners #441

Open
spiffxp opened this Issue Jan 12, 2019 · 3 comments

Comments

@spiffxp
Copy link
Member

spiffxp commented Jan 12, 2019

First part of #347

We'd like to ensure there are testgrid alerts setup for all jobs on the release-master-blocking dashboard (and release-master-upgrade). Those alerts should preferably go to a publicly accessible google group, staffed by a SIG.

Would be nice if the jobs had the owner in their description, as well as what they do.

For the tricky cases like upgrades-that-sig-cluster-lifecycle-refuses-to-own-and-only-a-few-google-people-but-usually-that-just-means-one-overburdened-person we can either make google groups, or add the individuals (testgrid supports multiple e-mail addresses IIRC?)

/assign @BenTheElder @mariantalla
Would like CI Signal to push this with Release lead shadow.

/milestone v1.14
/kind documentation
/sig release
/sig testing

@BenTheElder

This comment has been minimized.

Copy link
Member

BenTheElder commented Jan 12, 2019

I wish I could favourite issues :-)

TestGrid does support multiple addresses.

@spiffxp

This comment has been minimized.

Copy link
Member Author

spiffxp commented Jan 22, 2019

I've opened kubernetes/test-infra#10870 to get my guesses out for review

@spiffxp

This comment has been minimized.

Copy link
Member Author

spiffxp commented Jan 22, 2019

/area release-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment