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

Add the contact information in case of job issue it will send out a notification #1216

Closed
cpanato opened this issue Sep 4, 2020 · 14 comments
Assignees
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@cpanato
Copy link
Member

cpanato commented Sep 4, 2020

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

@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 4, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Sep 4, 2020
@k8s-ci-robot
Copy link
Contributor

@cpanato: The label(s) area/ci cannot be applied, because the repository doesn't have them

In response to this:

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.

Parent issue: #1215

/area release-eng
/area ci
/kind documentation
/priority important-soon
/milestone v1.20

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.

@cpanato
Copy link
Member Author

cpanato commented Sep 4, 2020

will close because it is a duplicate of kubernetes/test-infra#18551

/close

@k8s-ci-robot
Copy link
Contributor

@cpanato: Closing this issue.

In response to this:

will close because it is a duplicate of kubernetes/test-infra#18551

/close

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.

@alejandrox1
Copy link
Contributor

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.
/reopen

@k8s-ci-robot
Copy link
Contributor

@alejandrox1: Reopened this issue.

In response to this:

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.
/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Sep 10, 2020
@cpanato
Copy link
Member Author

cpanato commented Nov 3, 2020

/assign

@cpanato
Copy link
Member Author

cpanato commented Dec 10, 2020

added this to my next week backlog

@saschagrunert saschagrunert changed the title 🏃 Add the contact information in case of job issue it will send out a notification Add the contact information in case of job issue it will send out a notification Dec 11, 2020
@saschagrunert
Copy link
Member

Took my freedom to rename the issue to optically match with others.

@LappleApple
Copy link
Contributor

LappleApple commented Jan 19, 2021

To check on which jobs are done...

/assign @puerco

@k8s-ci-robot
Copy link
Contributor

@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.
For more information please see the contributor guide

In response to this:

/assign @puerco to check on which jobs are done

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.

@saschagrunert
Copy link
Member

/milestone v1.21

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.20, v1.21 Jan 19, 2021
@hasheddan
Copy link
Contributor

@cpanato is this issue scoped to all CI or just sig-release? It looks like we are currently covered for sig-release baords.

@cpanato
Copy link
Member Author

cpanato commented Apr 13, 2021

just sig-release. and you are right, i forgot to close this

/close

@k8s-ci-robot
Copy link
Contributor

@cpanato: Closing this issue.

In response to this:

just sig-release. and you are right, i forgot to close this

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants