-
Notifications
You must be signed in to change notification settings - Fork 397
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 the contact information in case of job issue it will send out a notification #1216
Comments
@cpanato: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
will close because it is a duplicate of kubernetes/test-infra#18551 /close |
@cpanato: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
re-opening: this one is useful to work along the proposed work of kubernetes/test-infra#18599 and do what we can in the scope of sig release. |
@alejandrox1: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
added this to my next week backlog |
Took my freedom to rename the issue to optically match with others. |
To check on which jobs are done... /assign @puerco |
@LappleApple: GitHub didn't allow me to assign the following users: to, check, on, which, jobs, are, done. Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone v1.21 |
@cpanato is this issue scoped to all CI or just sig-release? It looks like we are currently covered for sig-release baords. |
just sig-release. and you are right, i forgot to close this /close |
@cpanato: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is to add contact information for existing jobs.
Some jobs do not have contact information so it cannot send out notifications when the job is having issues.
/area release-eng
/area ci
/kind documentation
/priority important-soon
/milestone v1.20
The text was updated successfully, but these errors were encountered: