On Tuesday, May 19, 2015 at 3:58:01 PM UTC+2, tps800 wrote:
>
> Hi!
>
> I'm having two jobs each one depends on the other and shall never build
> while the other one builds. Both are independend of each other except they
> are using the result of each:
>
> - cmake blocks building of llvm
> - llvm blocks building of cmake
>
> I've entered cmake as blocker in llvm, and llvm as blocker in cmake.
> Worked fine, until I managed to set jenkins up to compile
> FreeBSD_{8,9,10,current} -- really long lasting jobs taking from 3 to 7
> hours to finish. Now I ended up with cmake *and* llvm in the job queue. No
> problem so far I thought, but: both do not run, because cmake is annotated
> as being blocked by llvm and llvm is being blocked by cmake.
>
> Is this a bug with "Build Blocker Plugin" (
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin) or is
> this intentional. I interpreted "[...] blocking jobs by their names in
> the list of currently running builds [...]" as only considering running
> builds, not builds which are in the queue to be run. In this case this
> would be a bug within this plugin.
>
Yes, this is a bug within "Build Blocker Plugin". It takes the queue and
running jobs into account, fastly leading to a deadlock if all slots are
occupied. "Build Blocker Plugin" would only have to take RUNNING jobs into
account, ignoring queued jobs.
Any idea where to put this bug report for "Build Blocker Plugin"?
--
Thomas
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/2cc9cc53-7336-4f6c-bcca-c7d7a8965f81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
