Interface TestDistributionExtension
-
public interface TestDistributionExtensionTask extension for configuring test distribution.This extension is added with name "distribution" to all
Testtasks.Please refer to the plugin documentation for details.
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description Property<Boolean>getEnabled()Whether test distribution is enabled.Property<Integer>getMaxLocalExecutors()The number of executors to use for running tests on this machine.Property<Integer>getMaxRemoteExecutors()The number of remote executors that should be requested from the remote test execution infrastructure in order run the tests of this test task.SetProperty<String>getRequirements()The requirements that need to be fulfilled by executors in order to execute the tests of this test task.Property<Duration>getWaitTimeout()The duration the build waits for the remote test execution infrastructure to respond.
-
-
-
Field Detail
-
NAME
static final String NAME
The name of the extension added to each test task.- See Also:
- Constant Field Values
-
-
Method Detail
-
getEnabled
@Internal Property<Boolean> getEnabled()
Whether test distribution is enabled.This setting defaults to
false, which results in the task executing tests with the built-in non-distributed test infrastructure.- Returns:
- whether test distribution is enabled or not.
-
getMaxLocalExecutors
@Internal Property<Integer> getMaxLocalExecutors()
The number of executors to use for running tests on this machine.This setting defaults to
maxParallelForks. The number of local executors that can be used is limited bymaxWorkerCount. Setting this to 0 causes tests to be only executed on the remote test execution infrastructure.- Returns:
- the number of local executors to use.
-
getMaxRemoteExecutors
@Internal Property<Integer> getMaxRemoteExecutors()
The number of remote executors that should be requested from the remote test execution infrastructure in order run the tests of this test task.This setting has no default value meaning that as much remote executors as are possible should be requested. Setting this to zero causes tests to be only executed using local executors.
Note that setting this to a fixed number doesn't necessarily mean that this test task will get that many remote executors. It's just an indicator for the remote test execution infrastructure for how many executors it should try to make available to this test task. It may well be that this test task does not get any remote executors at all e.g. if no executors matching all
requirementsbecome available.- Returns:
- the number of remote executors to request.
-
getWaitTimeout
@Internal Property<Duration> getWaitTimeout()
The duration the build waits for the remote test execution infrastructure to respond.This setting defaults to 30 seconds and must be set to a positive value.
- Returns:
- the wait timeout duration.
- Since:
- 1.2
-
getRequirements
@Input SetProperty<String> getRequirements()
The requirements that need to be fulfilled by executors in order to execute the tests of this test task.Requirements are matched against the capabilities of the connected remote executors. Only those executors having all required capabilities will be assigned for running the tests of this task. Local executors are assumed to provide any capabilities. This means that no matter the requirements, local executors will always be used as long as
maxLocalExecutorsis greater than 0.A requirement String may only contain alphanumeric characters, dashes, underscores, periods, and a single equals sign. Apart from that, users are free in how they want to structure requirements. The recommendation is to use key value pairs or tag-like requirements:
test { distribution { requirements = ['os=linux', 'db=mysql', 'EXECUTOR_POOL_1'] } }The requirements will always have the value
jdk=<version>added with<version>being derived from the executable set on this test task viaTest.getExecutable().- Returns:
- the requirements remote executors need to fulfill for running tests of this test task.
-
-