Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13710

priority not applied on build triggered job immediately

XMLWordPrintable

      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.

            emsa23 Magnus Sandberg
            moncreaff Greg Moncreaff
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: