-
Notifications
You must be signed in to change notification settings - Fork 72
Update release gating documentation #366
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
Conversation
This documentation is quite old (still refers to build cop), this updates it to the latest guidelines from TRT for becoming a release informer or gating job.
@stbenjam: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
This does not block the release but you can run it often enough to get a decent signal. At least once a day, but every 6 | ||
or 12 hours is better. | ||
|
||
The job name should follow the [naming guidelines](/docs/how-tos/naming-your-ci-jobs/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
naming-your-ci-jobs
does not exist
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's there on master branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'll work when it's live: https://docs.ci.openshift.org/docs/how-tos/naming-your-ci-jobs/ exists
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DennisPeriquet, droslean, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
TRT-1036
This documentation is quite old (still refers to build cop), this updates it to the latest guidelines from TRT for becoming a release informer or gating job.