benchmark: fix GCS bucket path for fetching CI job logs #3770
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The benchmark tool was using the old "kubernetes-jenkins" GCS bucket to fetch job logs, but all CI jobs have been migrated to the "kubernetes-ci-logs" bucket as part of the k8s-infra migration.
This was causing the benchmark job (ci-perf-tests-kubemark-100-benchmark) to fail with "No matching dirs were found" errors when trying to fetch metrics from ci-kubernetes-e2e-gci-gce-scalability and ci-kubernetes-kubemark-100-gce jobs.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: