Stop running fallback Go autobuild if database is finalized #1405
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
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.
When we implemented Go extraction reconciliation, we added a step to autobuild Go in the
analyzeaction if the autobuilder was not already run, or if there were no custom build steps, to maintain backwards compatibility with customers who may not have set either. This PR adds logic to also not autobuild Go inanalyzeif a Go database has already been finalized — a finalized database directory may have been manually specified in theinitstep.I have not added a PR check to test, because I'm not sure this use case is common enough to check in a finalized database and justify adding another step to CI.
Merge / deployment checklist