-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Nightly performance tests #6036
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: 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. |
Subtask of #5452.
As part of tektoncd/community#602 and our goals for Pipelines V1 we'd like to have some way to regularly measure Pipelines performance. I think the easiest way to start out would be to create a periodic prow job (like our existing upgrade tests) that run some version of #4378. It doesn't have to be perfect-- we can adapt these tests as time goes on, and just having some form of regular performance measurement will be a great start.
The text was updated successfully, but these errors were encountered: