Conversation
The Build Cop Bot will open/close issues for failing/passing tests.
|
|
||
| # If we're running system tests, send the test log to the Build Cop Bot. | ||
| # See https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop. | ||
| if [[ $KOKORO_BUILD_ARTIFACTS_SUBDIR = *"system-tests"* ]]; then |
There was a problem hiding this comment.
Is this system-tests something that's on the kokoro end or is it searching for it here?
If searching here, it won't find it - we restructured the kokoro config files to be broken down by python version and then into continuous, periodic, presubmit, and lint, unlike before when we had system tests by product
There was a problem hiding this comment.
Good catch. Switched to continuous. Let me know if you'd prefer periodic.
There was a problem hiding this comment.
Sweet. They're all going to fail right away - we're slowly but surely resolving all failures within.
| if [[ $KOKORO_BUILD_ARTIFACTS_SUBDIR = *"continuous"* ]]; then | ||
| # Use the service account with access to the repo-automation-bots project. | ||
| gcloud auth activate-service-account --key-file $GOOGLE_APPLICATION_CREDENTIALS | ||
| gcloud config set project repo-automation-bots |
There was a problem hiding this comment.
Would it be better to use -project flag on the command below instead? Hopefully none of the samples are relying on gcloud to detect projects, but it might be safer to minimize side effects
The Build Cop Bot will open/close issues for failing/passing tests.