Use a single gradle command for customDetektRules#3123
Conversation
|
🎯 Code Coverage 🔗 Commit SHA: 53466ef | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #3123 +/- ##
===========================================
+ Coverage 70.69% 70.72% +0.02%
===========================================
Files 893 893
Lines 33000 33000
Branches 5549 5549
===========================================
+ Hits 23329 23336 +7
+ Misses 8120 8109 -11
- Partials 1551 1555 +4 🚀 New features to boost your workflow:
|
b39b0b4 to
53466ef
Compare
0xnm
left a comment
0xnm
left a comment
There was a problem hiding this comment.
Original reason for splitting it was getting Out Of Memory error (occasionally) when all tasks are run at once.
Let's see if we hit it still or not.
Yes, let's keep an eye on it. IIUC in CI gradle isn't running things in parallel, because this isn't enabled, so I'm not sure how it can start using too much memory. |
|
I mean it was still a single Gradle daemon invocation, so maybe some memory wasn't collected when a module task completes, or there is some in-memory growing cache. It wasn't about parallel tasks execution. |
3 participants
What does this PR do?
We can use a single gradle command to run the task in all gradle subprojects https://docs.gradle.org/current/userguide/multi_project_builds_intermediate.html#sec:executing_tasks_by_name.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)