Single Mercurial push triggers multiple builds

I'm observing that pushing a large number of changes into a mercurial repo sometimes triggers multiple builds of the same build task. The first build will contain a small subset of the changes, and only eventually will all changesets be included by later builds.

This is very confusing behavior, as the intermediate builds will often fail due to being random intermediate states of the source tree.

4 comments
Comment actions Permalink

Hi Christian

How is quiet period set in VCS settings?

0
Comment actions Permalink

120 seconds I believe... BTW, this is on TC 5.1.5 - working on upgrading...

0
Comment actions Permalink

Hi Christian

Is it reproduced in 6.5?

0
Comment actions Permalink

We haven't upgraded yet. Working on it ... see my posts about possible high availablility solutions.
--
cg

0

Please sign in to leave a comment.