Hi There I had the same issue and we areusing CC 1.4 for our CI, I think using the forcebuild in trigger will workout around this problem. what you say?
Kishore On Sep 3, 2:19 pm, DaveMoor <[EMAIL PROTECTED]> wrote: > I have the same issue but from the other side. I have a few projects > which force dependent projects, if the dependents are queued waiting > to check for modifications when the 'parent' tries to force them they > do not get built so my builds get out of sync. > > This happens every time on one of my project groups as the parent > takes so long to build all its children are waiting to check for > modifications. This has been raised before, I was waiting to upgrade > to version 1.4 to see if things had changed in this area. > > Dave > > On Sep 2, 2:41 pm, Alex <[EMAIL PROTECTED]> wrote: > > > Ok, I have a few Queue's with a lot of projects in them, so this may > > not be evident to a lot of people. But what I noticed today troubles > > me, in fact I would call it a bug. So if the ifModifcations has placed > > a project on the queue and it is in line and you force a build CC will > > throw away the force build. Therefore, if no modifications existed > > even if you force you may not get a build. This is really hard on me > > as the projects spend a lot of time in the queue so you really have to > > time your forced builds in some cases. I think when a forced build > > request comes in, if anything gets kicked out of the cube it should be > > the ifmodifications that is already there. Thoughts anyone?
