Improve logging for Go autobuild when invoked in analyze step
#1862
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
angelapwen
force-pushed
the
add-log-message
branch
from
2bef879
to
d36e2d5
Compare
angelapwen
force-pushed
the
add-log-message
branch
from
d36e2d5
to
ed44103
Compare
angelapwen
changed the title
analyze step
angelapwen
force-pushed
the
add-log-message
branch
from
ed44103
to
a0124a7
Compare
6 tasks
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.
We want to make it more explicit when we run the Go autobuilder in
analyzewhen the user has not specified the autobuild step. I have used thedebuglog level (which will show up when re-run on debug mode is activated) rather thaninfobecause we have customers on legacy workflows where this is the expected workflow.Merge / deployment checklist