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 to work out why the job has itself as an upstream job - this can be caused by the job downloading from the maven repo a previous version of its artifacts (e.g. you use dependency-copy for a jar in a module in the reactor, but you are not running package in jenkins) /James On Thursday, 14 March 2013 13:02:21 UTC, Jason Voegele wrote: > > Hi, recently many of our Jenkins jobs are stuck waiting for themselves to > finish executing before they can start executing. What I mean is that a > Maven job is in the queue to execute, but never actually does execute > because it says that it is waiting for itself to finish, even though it has > never started. See for example the attached screenshot. > > > Can anyone explain this recent behavior? Is it a Jenkins bug? > > -- > Jason Voegele > A child of five could understand this! Fetch me a child of five. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/groups/opt_out.
