-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore: enable Gradle build cache #1093
Merged
edgarvonk
merged 10 commits into
main
from
feature/PZ-2480-cache-frontend-build-artefacts-for-unit-tests
May 14, 2024
Merged
chore: enable Gradle build cache #1093
edgarvonk
merged 10 commits into
main
from
feature/PZ-2480-cache-frontend-build-artefacts-for-unit-tests
May 14, 2024
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
hsiliev
reviewed
May 13, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1093 +/- ##
=============================================
- Coverage 40.18% 18.81% -21.37%
+ Complexity 2214 697 -1517
=============================================
Files 913 913
Lines 18308 18308
Branches 1267 1267
=============================================
- Hits 7357 3445 -3912
- Misses 10502 14707 +4205
+ Partials 449 156 -293
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
edgarvonk
changed the title
chore: cache frontend build artefacts in GitHub workflow
chore: enable Gradle build cache
May 14, 2024
…they are the frontend is not re-built when running unit tests nor when generating code coverage reports
…they are the frontend is not re-built when running unit tests nor when generating code coverage reports
… fails with `sh: 1: jest: not found`
…e because it seems they are not
…e.json as they should not be (npmInstall already is)
…ause the npmRunBuild task gets executed again regardless
edgarvonk
force-pushed
the
feature/PZ-2480-cache-frontend-build-artefacts-for-unit-tests
branch
from
May 14, 2024 07:21
3ee15cc
to
eed5091
Compare
hsiliev
approved these changes
May 14, 2024
edgarvonk
deleted the
feature/PZ-2480-cache-frontend-build-artefacts-for-unit-tests
branch
May 14, 2024 10:02
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.
Enable Gradle build cache for faster development speed when working locally (especially when switching branches) and minor improvements to our build scripts.
Solves PZ-2480