File triggers, time triggers and process triggers are all delivered in FinalBuilder Servers web interface to support a range of agile development best practices. The number of triggers provides extensive options for automating build execution and to safeguard the automated execution of your build, you can also use trigger conditions to make each trigger pass a set of conditions before a build is run.
It’s easy to schedule builds with FinalBuilder Server. Through a visual property page, you can schedule builds to run daily, weekly or any interval you require. FinalBuilder’s developers have also carefully designed this feature to offer ease of use without restricting scheduling options. The screen shot below demonstrates the flexibility of the time trigger by scheduling a build to run every second weekday between 1 am and 4 am.
A flexible method for running builds when a special file or folder event occurs is also available with the file trigger. This trigger equips you to implement continuous integration without a version control system, trigger builds based on changes to a designated configuration file and much more. Run a build automatically when a file or folder is renamed, created, deleted or changes are made to size, system attributes, last write time, last access time or security permissions.
With the run process trigger, you can launch any Windows process and then execute a build based on the outcome of running that process. Trigger builds based on the process output, process exit code and/or file changes made while the process was in execution. This trigger opens up a range of possibilities for triggering builds and facilitates flexible project execution.
Trigger conditions are used to determine whether a trigger should start the build as soon as the project is triggered or whether it should have to pass a set of conditions before starting. The FinalBuilder Server trigger condition properties page offers flexible options for setting the condition type, the triggers to apply the condition to and what to do when conditions are not met.
A trigger condition can be applied to all triggers so that whenever a trigger tries to start a build, this condition will be evaluated. It can also be applied to all triggers and users so that every time a build is started, this condition will be evaluated (with the exception of a user by-passing the build queue when starting the build). Finally, conditions can also be applied only to a specific trigger.
If a condition is not met, you can specify the action to take. Discard the build to forget the build was ever triggered. Try again to start the build at a later time and re-evaluate the trigger conditions again.
FinalBuilder Server supports a range of source control systems to simplify the implementation of Continuous Integration. See which version control systems are supported and learn more about Continuous Integration with FinalBuilder Server in the Continuous Integration Section
Back to the FinalBuilder Server feature tour overview
