Oliver, Thank you for the response.
I tried the tests listed in your link https://github.com/jenkinsci/selenium-tests/blob/master/features/matrix.feature#L48 @since(1.515) Scenario: Use Job parameters in combination filters Given a matrix job When I configure the job And I configure user axis "run" with values "yes maybe no" And I set combination filter to "run=='yes' || (run=='maybe' && condition=='true')" And I add a string parameter "condition" And I save the job And I build the job And I set "condition" parameter to "false" And I click the "Build" button And I build the job And I set "condition" parameter to "true" And I click the "Build" button Then combination "run=yes" should be built in build 1 Then combination "run=yes" should be built in build 2 Then combination "run=maybe" should not be built in build 1 Then combination "run=maybe" should be built in build 2 Then combination "run=no" should not be built in build 1 Then combination "run=no" should not be built in build 2 However, in my Jenkins 1.538 instance, I am not observing these results. Whether or not I pass in false or true, all three (yes, maybe, no) are triggered. See the attachments and let me know if I am taking the combination filter syntax in the test too literally or am otherwise missing something. I tried some other variations but still receive the same results. config.xml <http://jenkins-ci.361315.n4.nabble.com/file/n4680230/config.xml> configuration_matrix_and_combo_filter.jpg <http://jenkins-ci.361315.n4.nabble.com/file/n4680230/configuration_matrix_and_combo_filter.jpg> build1_param_was_false.jpg <http://jenkins-ci.361315.n4.nabble.com/file/n4680230/build1_param_was_false.jpg> build1_all_3_configs_run.jpg <http://jenkins-ci.361315.n4.nabble.com/file/n4680230/build1_all_3_configs_run.jpg> build2_param_was_true.jpg <http://jenkins-ci.361315.n4.nabble.com/file/n4680230/build2_param_was_true.jpg> build2_all_3_configs_run.jpg <http://jenkins-ci.361315.n4.nabble.com/file/n4680230/build2_all_3_configs_run.jpg> The only way I can get "maybe" and "no" to be skipped/not triggered is to change the filter to run=='yes' || (run=='maybe' && false) which of course does me no good. Any guidance you can provide is appreciated. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/job-parameters-in-combination-filter-not-working-always-evaluate-to-true-tp4679943p4680230.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
