![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Attachments:
|
Screen Shot 2013-05-27 at 9.09.20 AM.png |
|
Components:
|
build-pipeline |
|
Created:
|
27/May/13 7:22 AM
|
|
Description:
|
I have set option "Restrict trigger to the most recent build" to "Yes".
See attached screen dump.
The "Memphis - Release" downstream from "Memphis - Dev #37" does not have a trigger - this works as expected since "Memphis - Dev #37" failed.
The "Memphis - Release" downstream from "Memphis - Dev #36" does have a trigger - this works as expected since "Memphis - Dev #36" is the latest successful build.
But, the "Memphis - Release" downstream from "Memphis - Dev #33, #34, #35" also have a trigger - this does not work as expected since "Restrict trigger to the most recent build" is set to "Yes". I would expect those not to have a trigger as they are not the latest successful build.
|
|
Environment:
|
CentOS, Jenkins 1.515
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jonas Bang Christensen
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
