|
||||||||
|
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/d/optout.
@bruce_rust: You said:
Job B is triggered off of a SCM poll and so gets the latest Job A build at the time (which is build 9)
This is in contrary to:
Job B may be triggered, as you say, off of an SCM poll, while Job A is building, but then the Build of Job B must remain in the wait queue. Job B is set to have the two properties above, so it must not start while Job A is running. No matter how many SCM polls/hooks/triggers there are.
I corrected small things pointing into this direction in the story description. If you think I misread what you meant, I kindly ask you to clarify it referring to this comment.
For your reference, the repositories of Job A and Job B are completely different. But from my point of view this does influence the core issue here, that is, Build B starts before Build A is completely finished.