Add a prow-kubemark job and see what happens
@@ -362,6 +362,8 @@ test_groups:
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-kubemark-100-gce
- name: ci-kubernetes-kubemark-100-canary
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-kubemark-100-canary
+- name: ci-kubernetes-kubemark-5-prow-canary
+ gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-kubemark-5-prow-canary
- name: ci-kubernetes-kubemark-5-gce
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-kubemark-5-gce
- name: ci-kubernetes-kubemark-5-gce-last-release
@@ -3970,6 +3972,10 @@ dashboards:
test_group_name: ci-kubernetes-kubemark-100-canary
code_search_url_template:
url: https://github.com/kubernetes/test-infra/compare/<start-custom-0>...<end-custom-0>
+ - name: kubemark-canary-prow
+ test_group_name: ci-kubernetes-kubemark-5-prow-canary
+ code_search_url_template:
+ url: https://github.com/kubernetes/test-infra/compare/<start-custom-0>...<end-custom-0>
- name: scalability-canary
test_group_name: ci-kubernetes-e2e-gce-scalability-canary
code_search_url_template:
