[JIRA] (JENKINS-17176) The Restrict matrix execution to subset Groovy filter is not evaluate
cjo9900 commented on JENKINS-17176 The Restrict matrix execution to subset Groovy filter is not evaluate Comments from the pull request This should not be evaluated here as the MatrixSubsetAction filter should be referring to the triggered matrix project, so in most cases this will return false as the AXIS that the matrix project has will not be available which are the normal cases for checking. So it can only reliably be checked in the Matrix project build. Actual evaluation takes place in the Matrix build in https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/matrix/MatrixBuildListenerImpl.java Thanks but for the evaluation, this Class is not called during the process. Should be called from DefaultMatrixExecutionStrategyImpl.java in a Matrix project from the static function in the hudson.matrix.listeners.MatrixBuildListener class. https://github.com/jenkinsci/jenkins/blob/6d95e3680c8edf49c2353633dd9c1a7072440989/core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java#L123 Sure but in my case, I have a freestyle project with a parameterized trigger configurations in post-build action to determine which build to launch next. I have to evaluate the Groovy filter which is never done in that case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17176) The Restrict matrix execution to subset Groovy filter is not evaluate
cjo9900 commented on JENKINS-17176 The Restrict matrix execution to subset Groovy filter is not evaluate From your use case it seems that you want to run the filter against the current build variables to allow/prevent the downstream build to trigger. If this is the case you should look at the run condition branch and create a groovy run condition. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17176) The Restrict matrix execution to subset Groovy filter is not evaluate
Adrien Lecharpentier
created JENKINS-17176
The Restrict matrix execution to subset Groovy filter is not evaluate
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
12/Mar/13 2:02 PM
Description:
The "groovy filter" value of the "Restrict matrix execution to subset" is never evaluated. So we cannot use this feature to trigger different jobs depending on a variable value by setting the filter to "${VAR}".contains("alu").
I'm preparing a pull-request for this. I will update the issue then.
Project:
Jenkins
Priority:
Major
Reporter:
Adrien Lecharpentier
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
