Phone - Australia: 1300 553 313
Hotline - New Zealand: 0800 450 168

VSoft - FinalBuilder


Focus on writing great software. Let FinalBuilder take care of the build.

Automating your Build process is simple with FinalBuilder. With FinalBuilder you don't need to edit xml, or write scripts. Visually define and debug your build scripts, then schedule them with 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.

If you are not using FinalBuilder to automate your builds, you are missing out.

FinalBuilder's Graphical Interface

The FinalBuilder Interface

FinalBuilder's core interface elements are the:

  • Action Types Tab
  • Action Lists
  • Run Tab and
  • Build Log

FinalBuilder's interface is dockable and completely customizable. To the right is a screenshot of the default layout. You can refer back to this screenshot (click to enlarge) to see which dock zone each of the interface elements belongs to by default.

Action Types Tab

FinalBuilder provides more than 600 pre-written scripts, called actions. Actions can interop with compilers, version control systems & testing tools, perform file operations and much more.

To automate each stage of a build process, actions can be combined into an action list. The "Actions" tab lists every action that can be added to your build project.

To quickly find the aciton you require, there is a "Search" box at the top of the Actions tab. You can search for actions by action name eg. Build VS.Net Solution, product name eg. Visual Studio or category eg. Compiler.

To add an action to your build project, click on it or drag-and-drop it into and Action List.

Main Action List

The main action list is where you define your build script. The build process will consist of a set of actions, which are executed from the top to the bottom during a build process.

Actions may be laid out in a parent/child hierarchy to add structure to your build process. In the example to the right, some nodes of the build process from above have been collapsed ("Try" and "Catch") to focus attention on the steps in the "Finally" action group.

The OnFailure action list is a special list of actions which get executed only if your build fails. OnFailure actions typically "clean up" so that the next build runs without error (eg. Check files back into version control).

Executing a Build

To run a build, click the run button on the toolbar, or select the Run menu option from the Run menu.

Running a build puts the FinalBuilder IDE into a build running state where it automatically selects the current action being executed as well as displaying logging information in the build log (see below).

When a build is running you cannot edit any actions, but you can change tabs at the bottom of the IDE so you can access the Run Status, or Watches for example. You can pause or stop a build using the Run menu or the toolbar buttons.

Build Log

The build log is where the output and logging messages of a build are stored.

The log is organised in the same hierarchy as your build process and records all the timing, status, and messages which occurred during the build.

The build log is updated in real time, so that you can watch the progress of the build.



Graphical Interface
FinalBuilder presents your build process in a logically structured, graphical interface. Any software developer can define and maintain their build with FinalBuilder, without needing to learn a new XML schema or language.

600+ Actions
With its extensive library of pre-written actions, FinalBuilder has an action to automate every common task in your build process. It also integrates with your existing compilers, version control systems and testing tools.

Flow Control
FinalBuilder includes Try and Catch actions for localised error handling as well as all the loops and conditional statements you get in a full programming language.

Scheduled Builds
FinalBuilder provides tight integration with the windows scheduling service, which allows builds to be scheduled to run daily, weekly or whenever you wish.

Integrated Debugging
A debugging engine is fully integrated into the FinalBuilder IDE. You can step between actions, set break points and set variable watches to debug your build process.

Detailed Logging
Output from all actions in the build process is directed to the build log. The log maintains the same tree structure as the action lists, which makes it easy to navigate the log file. Logs can be exported in HTML, XML or text formats.
Email, MSN, FTP & SFTP Support
Your build process can email the results of the build to you. For example, if the build fails it can export the log, attach it to an email and send it to you. You can announce successful builds on NNTP news servers.

Using variables is the key to making your build process dynamic. Use variables to pass information from one action to another, and enable actions to build with user specific or machine specific values.

Version Control Integration
FinalBuilder supports more than a dozen version control systems out-of-the-box, so it can get, checkout, tag and perform other build related operations with your existing revision control system.

Scripting Support
Each FinalBuilder action exposes a number of script events, where you have access to all the properties of the action using VBScript, JavaScript, Powershell or Iron Python. In addition, the "Run Script" action allows you to perform specific tasks which might not be covered by the built in action types.

Action Studio
Action Studio is an IDE for writing custom FinalBuilder actions. It provides a way to extend the built-in functionality in FinalBuilder. Action Studio is included in FinalBuilder and can be accessed under the "Tools" menu.

Continuous Integration Server
FinalBuilder Professional includes a full featured Continuous Integration and Automated Build server to build and test your code the moment it is checked-in to version control.



For more information please contact the MicroWay sales team: buynow
Head Office
MicroWay Pty Ltd
PO Box 84,
Braeside, Victoria, 3195, Australia
Ph: 1300 553 313
Fax: 1300 132 709
email: sales@microway.com.au
ABN: 56 129 024 825
Sydney Sales Office
MicroWay Pty Ltd
PO Box 1733,
Crows Nest, NSW 1585, Australia
Tel: 1300 553 313
Fax: 1300 132 709
email: sales@microway.com.au
ABN: 56 129 024 825
New Zealand Sales Office
MicroWay Pty Ltd (NZ)
PO Box 912026
Victoria Street West
Auckland 1142, New Zealand
Tel: 0800 450 168
email: sales@microway.co.nz

International: call +61 3 9580 1333, fax +61 3 9580 8995

© 1995-2022 MicroWay Pty Ltd. All Rights Reserved. Terms and Privacy Policy.