You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

A Repository Trigger is used to trigger a Configuration when a change is committed to the repository you specify in the trigger.

Setting up a trigger for a non distributed version control system will give you the following options:

The only additional parameter you get is the Quiet Period. When a change set is detected on a repository you set the trigger up to monitor, a build is created and put in the Build Queued state. It sits in the queued state until the quiet period expires. While in the quiet period, additional commits to the repository won't trigger new builds but instead append those change sets to the build that's in the quiet period.

 

 

 

 

 

 

 

 

 

 

 

  • No labels