...
Repository triggers are used to trigger a configuration when a change is committed to a certain repository.
| Table of Contents |
|---|
Repository Trigger Options
This section describes the Build Completed Trigger options. Visit the Triggers page for information regarding options such as 'Build Priority and 'Force Repository Check', which are shared by all trigger types.
...
- Latest: This will only link the latest changeset to the build.
- All since last successful build: This will add all the changesets that have occurred in other repositories since the last successful build, to the current build.
For example, let say my configuration is linked to a repository called myNonTriggeringRepository and this repository is not linked to a repository trigger. Since the last time a build was executed successfully, I have made the following checkins to the source code in myNonTriggeringRepository:
...
- With Associate Changesets set to 'Latest': Fixed annoying deadlock bug. issue #3199.
- With Associate Changesets set to 'All since last successful build': Fixed annoying deadlock bug. issue #3199, Minor UI fixes, fixed show stopper bug #544.
Branch Aware Version Control System Options
The options for a Repository Trigger differ slightly depending on the type of the selected repository. If it's a branch aware repository (Mercurial,Git, Subversion, PlasticSCM) you will get additional options such as which branches will trigger a build.
...