Run ci.jenkins.io tests in parallel #294
Merged
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
Save time and money by testing in parallel with all the cores available
on agents of ci.jenkins.io.
Allow developer control of parallel testing
Developers are allowed to configure the amount of parallel testing based
on the configuration and use of their computer. This allows developers
to configure test parallelism based on their environment and still allow
ci.jenkins.io to reduce costs by running tests in parallel.
Developers can adjust parallel execution by passing a command line
argument to Maven like this:
mvn clean -DforkCount=1C verify
Developers can define a Maven profile that sets the forkCount in their
~/.m2/settings.xml like this:
<profile>
<id>faster</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<forkCount>.45C</forkCount>
</properties>
</profile>
With that entry in the settings.xml file, then 0.45C will be used for:
mvn clean verify
Supersedes jenkinsci#283
alecharp
approved these changes
Sep 18, 2023
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.
Run ci.jenkins.io tests in parallel
Save time and money by testing in parallel with all the cores available on agents of ci.jenkins.io.
Allow developer control of parallel testing
Developers are allowed to configure the amount of parallel testing based on the configuration and use of their computer. This allows developers to configure test parallelism based on their environment and still allow ci.jenkins.io to reduce costs by running tests in parallel.
Developers can adjust parallel execution by passing a command line argument to Maven like this:
mvn clean -DforkCount=1C verify
Developers can define a Maven profile that sets the forkCount in their ~/.m2/settings.xml like this:
faster true .45CWith that entry in the settings.xml file, then 0.45C will be used for:
mvn clean verify
Supersedes #283
Testing done
Confirmed tests pass on Java 11, Java 17, and Java 21 with forkCount=1C on my Linux computer.
Rely on ci.jenkins.io to test Windows.
Submitter checklist