Multiple VCS roots with differing checking intervals

Hi

I have a build with two VCS roots attached that have different checking intervals set, and I'm finding that the longer of the two intervals seems to apply when queuing the build, whichever underlying repo is changed - is this as expected ?

For example:
   build B uses files from repositories R1 and R2 accessed via VCS roots V1 and V2 ;
   V1 has its checking interval set to the default (60 seconds)
   V2 has its checking interval set to 3600 seconds
   a change is made in repo R1
   within a minute build B is flagged as having a pending change
   but, build B is not actually added to the build queue for another ~3600 seconds


RB

6 comments
Comment actions Permalink

Hi,

Yes, this is "by design". TeamCity cannot check for changes more frequently than specified checking for changes interval. The maximum checking for changes interval among the build configuration VCS roots should pass, because TeamCity must ensure that changes were collected at least once for every VCS root.
If you think that it's a usability issue, please feel free to create a request in our tracker: https://youtrack.jetbrains.com/issues/TW.

0
Comment actions Permalink

Thanks, as you say the current behaviour makes sense.

Maybe worth a note in the documentation where it describes setting this value.

0
Comment actions Permalink

Thank you for you feedback! We added a note to the documentation.

0
Comment actions Permalink

Sorry to continue an old post.

The current documentation does not seem to mention this anymore, the documentation seems to have changed between the following versions

Does this mean the behavior changed as well? I can't find it in the change list.

Thanks for clarifying this.

0
Comment actions Permalink

Hi Hans,

 

indeed the behavior was changed as well, since we now force a check for changes independently of the interval when pending changes for a build are detected on any of its vcs roots. 

 

Do you have any issues with the new behavior or were just looking for confirmation?

0
Comment actions Permalink

Hi Denis,

It was more to get it confirmed that it changed, as I couldn't find it back in the release report.

We still use an older version of TeamCity and have a configuration that has 2 VCSs, one of those will hardly change, so was planning to suggest to put the interval to a day. But as I understand it that could delay running the configuration for the server version we have, this is not what we want so kept the interval low for now.

So no, no problem. I think the new behavior is better, I just can't use it till we upgrade.

0

Please sign in to leave a comment.