Page tree
Skip to end of metadata
Go to start of metadata

Before reading this page, it is highly recommended you read the Triggers page.

Repository triggers are used to trigger a configuration when a change is committed to a certain repository.

Repository Trigger Options

Repository

The repository related to this trigger (these are presented on the 'Repositories' tab).

Quiet Period

When a changeset is detected on the selected repository, a build is created and put in the Build Queued state. It waits in a queued state until the quiet period expires. While in the quiet period, additional commits to the repository will not trigger new builds, however these new changesets will be added to the build that is currently in the quiet period.

This feature is particularly useful when you want to group a set of quickly committed changes into a single build.

The Quiet Period is specified in minutes, and defaults to 5 Minutes.

Associate Changesets

Identifies which Changesets should be associated with this build (relevant for all other non-triggering repositories). Non-triggering repositories are all repositories linked to the current configuration, that did not activate this triggering.

There are two options for associate Changesets:

  • 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.

For example, Lets assume 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: 

  • Fixed deadlock bug. issue #3199.
  • Minor UI fixes
  • fixed show stopper bug #544

With these checkins, lets assume that Fixed annoying deadlock bug. issue #3199 is the latest checkin to be made.

On my configuration I have a second repository called myTriggeringRepo which has a repository trigger that will execute a build every time a checkin is made to myTriggeringRepo.

What I have selected for Associate Changesets will change the latest changesets that I will see associated with my builds.

For this example, a build is triggered by a change being detected in myTriggeringRepo. Once the build has finished running, if I check the latest changes made in myNonTriggeringRepository, I will see the following checkins:

  • With Associate Changesets set to 'Latest':  Fixed deadlock bug. issue #3199.
  • With Associate Changesets set to 'All since last successful build': Fixed deadlock bug. issue #3199, Minor UI fixes, fixed show stopper bug #544.

You also get the option to only send notifications to users who triggered the build.

Trigger Branch (for branch-aware repositories)

For branch-aware repositories, this option allows you to further refine the branches to observe as part of this trigger.  The options here are: 'All branches', 'Default branch' (as specified within the repository options page), and 'Pattern matched branches'. 

All Branches

 

When this option is selected, the trigger will start a build if any changes are made to any branch. You also get the option to only send notifications to users who triggered the build.

Default Branch

 

When this option is selected, the trigger will start a build if a change was made to the repository's default branch. The default branch is specified within the Repository Options.

Pattern matched branch

When this option is selected, the trigger will start a build when a change is made to a branch and the full branch path matches the regular expression you supply. 

The regular expression entered in the screen shot below is ^feature-.*. This will match any branch in a Git or Mercurial repository that starts with feature-

Note that the regular expression matches against the full branch path which depends on the repository type as follows:

Git and Mercurial:              branchname
TFS and Plastic SCM:         /branchname
Subversion:                        /branches/branchfolder/

So the pattern in the above example would be ^/feature-.* for TFS and Plastic SCM and ^/branches/feature-.* for Subversion.

Trigger Tags (for tag-aware repositories)

 

Note triggering on tags is only available as from version 1.5

Trigger On Tag Changes

Determines how to treat tag changes.  Options here include: 'Dont trigger on tag changes',' For all Tags', 'For tags matching pattern'.

Dont Trigger on Tag Changes

Do not trigger when a tag change is detected.

For All Tags

When this option is selected, a page of additional options will appear. If at least one of the conditions is met, a build will be initiated. Please note the tag detection must also be enabled in the settings for the selected repository.

Trigger on new tags

When a new tag is detected, a new build will be triggered .

Trigger on tag deletions

When a tag is deleted, a new build will be triggered.

Trigger on tag movements 

When a tag is moved from one changeset to another, a new build will be triggered.

Include Tag changes made by ContinuaCI 

Tags can be manipulated by the Continua system itself (for example by an Event Handler).  If tag changes of this nature should trigger a build, select this option.  Please note that the options above (eg trigger on new tags) will be taken into account.  For example if the 'Trigger on new tags' option was selected as well as the 'Trigger on tag changes made by Continua CI', then new tags made by the Continua system user will trigger a build.  Tag changes made by the Continua user are ignored by default.

Only Trigger on Tag Changes

Ignore changesets which are not the result of a tag change.

For Tags Matching Pattern

When this option is selected, a page of additional options will appear. If at least one of the conditions is met, a build will be initiated. Please note the tag detection must also be enabled in the settings for the selected repository. 

Tag Pattern

A regular expression pattern defining which tags to consider

Trigger on new tags

When a new tag is detected, a new build will be triggered .

Trigger on tag deletions

When a tag is deleted, a new build will be triggered.

Trigger on tag movements 

When a tag is moved from one changeset to another, a new build will be triggered.

Include Tag changes made by ContinuaCI 

Tags can be manipulated by the Continua system itself (for example by an Event Handler).  If tag changes of this nature should trigger a build, select this option.  Please note that the options above (eg trigger on new tags) will be taken into account.  For example if the 'Trigger on new tags' option was selected as well as the 'Trigger on tag changes made by Continua CI', then new tags made by the Continua system user will trigger a build.  Tag changes made by the Continua user are ignored by default.

Only Trigger on Tag Changes

Ignore changesets which are not the result of a tag change.

 

 

 

  • No labels