Trigger with quiet period builds without fixed revisions
Hi there,
Is there a way to set up a quiet period of say 2 minutes, but to have the builds triggered still use the ‘latest change when build starts’ mode instead of a fixed revision?
We'd still like builds to be triggered fairly quickly after a change is submitted, though _some_ quiet period is useful to give people a chance to submit accidentally omitted files, or related commits that depend on each other. However for our particular setup we only ever want builds to be done from the latest commit (I did see the ‘optimize’ setting where they can be replaced too, but does that take a quiet period into account too?).
Or alternatively, is there a way to avoid builds being triggered/queued while one is in progress? Since that would also accomplish the same thing
Cheers,
Geordie
Please sign in to leave a comment.
I think that existing options should allow you to achieve the desired behavior:
1. Per-checkin triggering: when this option is not enabled, several check-ins by different committers can be made; and once they are detected, TeamCity will add only one build to the queue with all of these changes.
2. Quiet period: 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.
3. Build Queue Optimization Settings: TeamCity optimizes the build queue: already queued build can be replaced with an already started build or a more recent queued build.
They all take into account each other. For example, if multiple pending changes are detected, the quiet period starts, and additional changes are detected, which makes the quiet period start again. Let's say this time, the quiet period finishes, and a build is added to the queue, but before it can start, the new changes are detected, which will replace the build with a new one (if optimization is enabled).
Please let me know if you have additional questions.
Best regards,
Anton