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

☂️ CI Policies improvements #1215

Closed
3 tasks
cpanato opened this issue Sep 4, 2020 · 3 comments
Closed
3 tasks

☂️ CI Policies improvements #1215

cpanato opened this issue Sep 4, 2020 · 3 comments
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 an issue that will cover the work that needs to be complete in order to have some CI policies and improvements.
We have a previous issue to describe, but now we know a little bit more so we are creating this issue and the child issues to cover some actions we will do in the following weeks

  • For existing Job: add the contact information in case of job issue it will send out a notification - GH Issue
  • Describe and write down the CI policy. Possible place for this information - GH Issue
  • Add a presbumit job to validate if updated jobs/new jobs follow the policy and have the necessary information. - GH Issue

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

/cc @hasheddan @puerco @alejandrox1

@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. labels Sep 4, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Sep 4, 2020
@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label 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 an issue that will cover the work that needs to be complete in order to we have some CI policies and improvements.
We have a previous issue to describe, but now we know a little bit more so we are creating this issue and the child issues to cover some actions we will do in the following weeks

  • For existing Job: add the contact information in case of job issue it will send out a notification - GH Issue
  • Describe and write down the CI policy. Possible place for this information - GH Issue
  • Add a presbumit job to validate if updated jobs/new jobs follow the policy and have the necessary information. - GH Issue

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

/cc @hasheddan @puerco @alejandrox1

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.

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

No branches or pull requests

2 participants