[
https://issues.jenkins-ci.org/browse/JENKINS-12923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159614#comment-159614
]
Hansgeorg Schwibbe edited comment on JENKINS-12923 at 2/28/12 2:00 PM:
-----------------------------------------------------------------------
According to the screenshot:
If "deployMocks" is deactivated, the Job is running in an endless loop until
"deployMocks" will be activated.
was (Author: haschwib):
If "deployMocks" is deactivated, the Job is running in an endless loop
until "deployMocks" will be activated.
> Job is locked if one of the triggered projects is deactivated
> -------------------------------------------------------------
>
> Key: JENKINS-12923
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12923
> Project: Jenkins
> Issue Type: Bug
> Components: parameterized-trigger
> Affects Versions: current
> Environment: OS: Linux 64-bit
> Jenkins Version: 1.447
> Parameterized Trigger Plugin Version 2.13
> Reporter: Hansgeorg Schwibbe
> Assignee: Kohsuke Kawaguchi
> Priority: Blocker
> Attachments: screenshot-1.jpg
>
>
> The "Trigger/call builds on other projects" build step locks the job if one
> of the "Projects to build" is deactivated.
> To reproduce:
> 1. Add the "Trigger/call builds on other projects" to the build steps.
> 2. Define some "Projects to build"
> 3. Activate the check box "Block until the triggered projects finish their
> builds"
> 4. Set "Mark this build as unstable if the triggered build is worse or equal
> to" to "UNSTABLE"
> 5. Deactivate one of the projects configured in "Projects to build"
> 6. Run the job
> Expected behaviour:
> The deactivated project will be ignored and the job continues with the next
> active project.
--
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
