Automating your build process with FinalBuilder is easy. With FinalBuilder, you don't need to edit xml or write scripts. Visually define and debug your build scripts, then schedule them with the Windows scheduler, or integrate them with Continua CI, Jenkins, or any other CI server.
Thousands of software developers rely on FinalBuilder to automate the build, test and release process.
FinalBuilder presents the build process in a logically structured graphical interface. Any software developer can use FinalBuilder to define and maintain builds without having to learn new XML schemas or scripting languages.
With its extensive library of pre-written scripts (called actions), FinalBuilder has an action that automates every common task in the build process. It also integrates with your existing compilers, version control systems and testing tools.
FinalBuilder includes Try and Catch actions for localized error handling, plus all the looping and conditional statements you get in a full programming language.
FinalBuilder provides tight integration with the Windows Scheduling Service, which allows builds to be scheduled to run daily, weekly, or any time you wish.
Integrated debugging
The debugging engine is fully integrated into the FinalBuilder IDE. You can step between actions, set breakpoints, and set variable watches to debug your build process.
The output of all operations during the build is directed to the build log. The log maintains the same tree structure as the action list, which makes navigating through the log files easy. Logs can be exported in HTML, XML or text format.
Your build process can email the build results to you. For example, if a build fails, it can export the log, attach it to an email and send it to you. You can announce a successful build on the NNTP news server.
Using variables is the key to making the build process dynamic. Use variables to pass information from one action to another and to enable actions to be constructed with user-specific or machine-specific values.
FinalBuilder supports over a dozen version control systems out of the box, so it can fetch, checkout, tag, and perform other build-related operations using your existing version control system.
Every FinalBuilder action exposes a number of scripting events where you can use VBScript, JavaScript, Powershell, or Iron Python to access all properties of the action. Additionally, the "Run Script" action allows you to perform specific tasks that might not be covered by the built-in action types.
Action Studio is the IDE for writing custom FinalBuilder actions. It provides a way to extend the built-in functionality in FinalBuilder. Action Studio is included with FinalBuilder and can be accessed under the Tools menu.