Overview

A project trigger is used to queue a build for a project when a particular event occurs. This event may be the passing of a specific length of time (e.g. trigger every 15 minutes), detection of a change to the projects source code, or some other event. Each project can have multiple triggers for different events.

Default Trigger

When a project is created, a trigger is automatically added to the project to monitor the project's SCM and trigger a build when a change to the source code is detected. If you do not want to monitor the project's SCM, you should modify or delete this default trigger.

Regular Build Schedules

To establish a regular build schedule, a cron trigger should be used. These triggers will fire at times described by a cron expression, popularised by the scheduling application found on many operating systems. For more information refer to the Project Cron Triggers page.

Project Dependencies

Two types of triggers may be used to manage dependencies between projects.

Dependent Build Trigger

A dependent build trigger is explicitly designed to trigger projects based on the dependencies configuration for the project. When a build of an upstream project completes, a dependency trigger will examine the status of the build. If the status is the same or more stable than the status configured in the dependency, the trigger will fire.

Build Completed Triggers

A build completed trigger can be used to trigger a build of a project when a build for another project completes. The trigger may be restricted to only fire for builds with certain states. This is a more direct trigger that is independent of the dependency configuration of the projects involved.

Pausing Triggers

If you wish to suspend operation of a trigger temporarily, it is simplest to pause the trigger. This can be done using the "pause" link in the corresponding row of the "triggers" table. To reactivate the trigger, use the "resume" link that replaces the "pause" link while a trigger is disabled.