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.
Changes
For our downstream service, we provide troubleshooting documentation for the user to determine the root cause of a failure. We there separate failures by step name. Since we rewrote the BuildRun message to not anymore contain the TaskRun reason, the step name is only shown at the end of the message in the
kubectl logs
command while we include the pod name earlier as well. I am slightly making a message change to also include the name of the step at the beginning of the message and not just in thekubectl logs
example which makes it easier to understand and extract the relevant data.Submitter Checklist
Release Notes