|
||||||||
|
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/d/optout.
I don't think we should implement this enhancement because it is counter to the way Jenkins represents job status. It would cause compatibility issues for users who depend on the meaning of the job status today. I think the set of users who depend on job status to be the status of that exact job is much, much larger than the set of users who would like a higher level concept of job status computed from the status of a set of branches.
I assume it could be implemented as an extension, which would make the behavior a job specific option, so that only those users who selected it would have the incompatible behavior. Even then, I don't think there is enough motivation to introduce the complexity of computing job status as an aggregate value from several builds.