Fix build cache for windows release build #731
Merged
Conversation
This file contains hidden or 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.
What do these changes do?
The
if ($GOOGLE_APPLICATION_CREDENTIALS)in the windows release script was not working. Furthermore the windows build uses the flags--discard_analysis_cache --notrack_incremental_state --nokeep_state_after_build --nouse_action_cacheto speed up the build.This PR removes those 'no cache' flags and enables the GCS cache.
How Has This Been Tested?
First run: timeout after 6 hours as expected: https://github.com/larq/compute-engine/actions/runs/2207868415
Second run: finish after 1 hour: https://github.com/larq/compute-engine/actions/runs/2218470790