Branch: refs/heads/master
Home: https://github.com/jenkinsci/conditional-buildstep-plugin
Commit: aa8b48e8ae93aa602f8b8c319943c0291d3b337e
https://github.com/jenkinsci/conditional-buildstep-plugin/commit/aa8b48e8ae93aa602f8b8c319943c0291d3b337e
Author: Rahul Somasunderam <[email protected]>
Date: 2023-08-05 (Sat, 05 Aug 2023)
Changed paths:
M Jenkinsfile
Log Message:
-----------
chore: Parallelize Tests (#73)
* chore: Parallelize Tests
This will use all available cores to run tests, and parallelize by all -
suite/class/method.
On machines with multiple cores, this will vastly improve test performance.
These times are on my M1 MBP with 10 (8P + 2E) cores. They were reported by
maven on running `mvn verify`.
I first ran `mvn verify` and ignored the time.
Then I ran it thrice without this change, and thrice with this change.
All times in seconds.
| | Run 1 | Run 2 | Run 3 | Average |
| ------ | ----: | ----: | ----: | ------: |
| Before | 21 | 21 | 22 | 21 |
| After | 16 | 16 | 16 | 16 |
| Savings| | | | 5 |
| % | | | | 24 |
* Move the forkCount definition into buildPlugin
Forcing the forkCount setting in the plugin pom will override the
value that a developer might set on their local computer based on the
configuration of that computer.
The configuration on ci.jenkins.io is known to have enough memory for
a JVM per core. Use JVM per core on ci.jenkins.io for faster testing
and reduced costs.
---------
Co-authored-by: Name From Git-Plugin-Test
<[email protected]>
Co-authored-by: Mark Waite <[email protected]>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/conditional-buildstep-plugin/push/refs/heads/master/418e35-aa8b48%40github.com.
