Greg Moncreaff created JENKINS-13710:
----------------------------------------
Summary: priority not applied on build triggered job immediately
Key: JENKINS-13710
URL: https://issues.jenkins-ci.org/browse/JENKINS-13710
Project: Jenkins
Issue Type: Bug
Components: prioritysorter
Reporter: Greg Moncreaff
Assignee: bklarson
I have jobs/priorities A (200), B (300), C (400)
A and B are using SCM trigger but diffing scope/time (A is a superset of B).
C is a downstream job of B that needs products that B leaves behind in the
workspace.
A cleans all workspace (clearcase private) files.
problem is that even though C is higher priority than A, if A is next in the
build Q, the priority application is too late and A starts before C so that
when C gets a chance to run, it fails as its needed inputs from the workspace
no longer exist.
--
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
