-
-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[breaking] Allow setting extra paths for build-cache #2612
Conversation
This change helps to better understand next commits.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2612 +/- ##
==========================================
+ Coverage 70.26% 70.30% +0.03%
==========================================
Files 222 222
Lines 21262 21304 +42
==========================================
+ Hits 14940 14977 +37
- Misses 5147 5151 +4
- Partials 1175 1176 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Massive work, good job!
Love all the combinations of flags in the integration tests!
832dc81
to
79d4f7f
Compare
Co-authored-by: Alessio Perugini <alessio@perugini.xyz>
79d4f7f
to
8797c63
Compare
555cf7c
to
94b1983
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM, left a single comment
Co-authored-by: Umberto Baldi <34278123+umbynos@users.noreply.github.com>
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
Allows to specify extra paths for build-cache to look for already build artifacts if they are not found in the default build-cache dir.
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
Yes.
Other information
Fix #2611