[
https://issues.jenkins-ci.org/browse/JENKINS-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacobo Jimenez updated JENKINS-13871:
-------------------------------------
Due Date: (was: 18/May/12)
> Using "Conditional build step" and "Parameterized build step" in same step is
> preventing parallel executions of same job
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-13871
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13871
> Project: Jenkins
> Issue Type: Bug
> Components: conditional-buildstep, parameterized-trigger,
> run-condition
> Affects Versions: current
> Environment: GNU/Linux x86_64 2.6.16.60-0.69.1-smp
> Tomcat
> Reporter: Jacobo Jimenez
> Assignee: domi
> Labels: diamond, exception, interlock, parallel, parameter, stuck
> Attachments: QueueInterlockTest_main#config.xml,
> QueueInterlockTest_subtask#config.xml
>
>
> Job A triggers a variable number of job B depending on a environment
> variable. It can be zero but since "Counter Parameter Factory" doesnt allow
> zero repetitions (Java exception) I had to include this step as a conditional
> build step. Job A must wait until the end of all B jobs so option "Block
> until the triggered projects finish their builds" is selected (because it is
> really a diamond execution).
> This jobs configuration works fine but if you launch another A (in parallel)
> when it finish its first step and reach conditional step, it get stuck
> waiting until the end of all the jobs from first execution, once first A
> execution finished second execution continue executing its B jobs.
> This is a kind of interlocking process between executions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
