Kokoro is not triggering on the define branch in the config #1561
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tulsishah
requested review from
sethiay,
vadlakondaswetha and
raj-prince
as code owners
sethiay
approved these changes
Dec 26, 2023
gargnitingoogle
pushed a commit
that referenced
this pull request
Jan 4, 2024
ashmeenkaur
pushed a commit
that referenced
this pull request
Jan 9, 2024
ashmeenkaur
pushed a commit
that referenced
this pull request
Jan 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Kokoro is not triggering on the define branch in the config. Kokoro is set up to use the commit hash from the parent configuration's branch for all subjobs, even if those subjobs with different branches. I have asked yaqs question on kokoro team but until it gets resolved we can use this workaround.
Link to the issue in case of a bug fix.
NA
Testing details