Quiet period definition and VCS trigger rules

Hello,

Documentation for TC 9.x describes quiet period as follows:

A quiet period is a period (in seconds) that TeamCity maintains  between the moment the last VCS change is detected and a build is added  into the queue. If new VCS change is detected in the Build Configuration  within the period, the period starts over from the new change detection  time. The build is added into the queue only if there were no new VCS  changes detected within the quiet period.

If I have a VCS trigger rule that is an exclusion (e.g. -:%SOME_PARAMETER%/Foo/bar.txt), if a change is made to a file that matches that rule during the quiet period, will the quiet period restart? It seems like it shouldn't, but I'd like to know what is the expected behavior by design.

Thanks,
Oleg.

5 comments
Comment actions Permalink

I also would like to know if there is any distinction between the very first change that starts the initial quiet period and subsequent changes as they relate to the exclusion rule. For example, no changes happen for a long time. A change comes in that exactly matches the exclusion rule. Will the quiet period timer start? I don't think it should.

0
Comment actions Permalink

Hi Oleg,

Quiet period does not take into account trigger rules and starts over when any new change is detected. This behavior is "by design". The main goal of quiet period is to ensure the project code consistency.
If there are no commits within the quiet period in files that are monitored by build configuration, then it most probably means that all the non-atomic check-ins are done and project can be built. If there are parts of the VCS root that should not be monitored then it is recommended to use checkout rules.

0
Comment actions Permalink

Hi Alina,

We are a little confused about your answer. "Quiet period does not take into account checkout rules and starts over when any new change is detected." and "If there are parts of the VCS root that should not be monitored then it is recommended to use checkout rules." seem to be contradictory. Could you please confirm if the following statements are correct?

1. Quiet period starts over when any new change is detected that matches attached VCS root(s) regardless of the checkout rules.
2. If there are parts of the VCS root that should not be monitored for sync during the build then it is recommended to use checkout rules.

0
Comment actions Permalink

Oleg,

Sorry, I misprinted, I wanted to say that quiet period did not take into account trigger rules (I corrected my answer).

1. Quiet period starts over when any new change is detected by TeamCity - the changes that you can see in UI. So checkout rules are taken into account.
2. "If there are parts of the VCS root that should not be monitored for sync during the build then it is recommended to use checkout rules". - Yes.

0
Comment actions Permalink

Now it makes sense. Thanks!


0

Please sign in to leave a comment.