-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
linux-x86-64 master, 4 slaves (mac, solaris, linux 32bit, win 32/64)
given:
several jdk versions are target of builds (compile, unittests, performance tests,...)
5x2 executors as stated
goal:
test all combinations (all jdks on each platform)
problem:
there are jdks which are not available for different platforms. for intel mac there is no jdk3 for example. the matrix job does substitute unavailable JDKs with the default from the executing computer WITHOUT stating the substitution to the user. This leads to redundant builds as well as to misinformation about the result of a combination (since it is done with a fallback jdk and not with the specified one).
current workaround:
use combination filter to limit execution. which is a very long piece of groovy. whenever the executor configuration changes, the long piece of groovy has to be adapted in each and every project. and that is really not the way for a build system like jenkins (i think)
feature request
offer a simple checkbox which allows the user to control whether default fallbacks should be used or not. Right next to the combination filter.
[JENKINS-11089] Allow control of fallback JDK usage
Florian Reimair
created issue -
Florian Reimair
made changes -
| Description |
Original:
given: several jdk versions are target of builds (compile, unittests, performance tests,...) 5x2 executors as stated goal: test all combinations (all jdks on each platform) problem: there are jdks which are not available for different platforms. for intel mac there is no jdk3 for example. the matrix job does substitute unavailable JDKs with the default from the executing computer WITHOUT stating the substitution to the user. current workaround: use combination filter to limit execution. which is a very long piece of groovy. whenever the executor configuration changes, the long piece of groovy has to be adapted in each and every project. and that is really not the way for a build system like jenkins (i think) |
New:
*given:* several jdk versions are target of builds (compile, unittests, performance tests,...) 5x2 executors as stated *goal:* test all combinations (all jdks on each platform) *problem:* there are jdks which are not available for different platforms. for intel mac there is no jdk3 for example. the matrix job does substitute unavailable JDKs with the default from the executing computer WITHOUT stating the substitution to the user. This leads to redundant builds as well as to misinformation about the result of a combination (since it is done with a fallback jdk and not with the specified one). *current workaround:* use combination filter to limit execution. which is a very long piece of groovy. whenever the executor configuration changes, the long piece of groovy has to be adapted in each and every project. and that is really not the way for a build system like jenkins (i think) *feature request* offer a simple checkbox which allows the user to control whether default fallbacks should be used or not. Right next to the combination filter. |
Jenkins IRC Bot
made changes -
| Component/s | New: matrix-project [ 18765 ] | |
| Component/s | Original: matrix [ 15501 ] |
| Workflow | Original: JNJira [ 141299 ] | New: JNJira + In-Review [ 175451 ] |