Thanks for the info James, but looking at the job configuration page the job
itself is not listed as either upstream or downstream of itself. Furthermore,
tracing through the upstream and downstream relationships identified by
Jenkins, there is no cycle and therefore the job is not upstream of i
Presumably you have "Block build when upstream project is building" enabled.
If so the reason is that the project has itself marked as an upstream
project.
This could happen if you trigger the job to run itself again (e.g. you want
a continous loop).
Assuming you haven't done that then you need
