RUM-3861 Update testing ci steps to limit OOM and memory usage#1986
Conversation
There was a problem hiding this comment.
why do we remove codecov? I find it useful, I rely on the data I receive for each PR to see the coverage change and if any files touched in the PR are not covered enough.
There was a problem hiding this comment.
Codecov was run as part of the kover job that we agreed to remove.
There was a problem hiding this comment.
What I'll do is replace the test:release with test:kover then
| # Manually build the java bytecode | ||
| - name: Execute Gradle build | ||
| run: ./gradlew assembleLibraries | ||
| run: ./gradlew assembleLibrariesDebug |
There was a problem hiding this comment.
ideally we still need to build both build types (because it is a security scan, it needs to cover everything) or at least release build type instead of debug, because release is what will be used by the customer later.
There was a problem hiding this comment.
Good point I'll switch to release
|
|
||
| ```shell script | ||
| ./gradlew assembleLibraries | ||
| ./gradlew assembleLibrariesDebug assembleLibrariesRelease |
There was a problem hiding this comment.
let's maybe still keep assembleLibraries? it is for the local run, without the agent, so we can run everything at once.
7bf4beb to
7213c49
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #1986 +/- ##
===========================================
+ Coverage 83.68% 83.73% +0.05%
===========================================
Files 487 487
Lines 17736 17726 -10
Branches 2663 2662 -1
===========================================
Hits 14842 14842
+ Misses 2167 2160 -7
+ Partials 727 724 -3 |
7213c49 to
c85c004
Compare
3 participants
What does this PR do?
Updates our CI to