Global Extension Configuration in BuildMaster
A number of the extensions included with BuildMaster have global settings that may be configured in addition to what is displayed on any Action Editors. For example, the .NET extension configuration includes fields for specifying the installed location of the .NET Framework as well as the Windows/.NET SDK location. If not specified, the extension will try to automatically determine appropriate values.
How to Determine when Global Settings are Available
If you are editing an Action, simply look for the Extension Configuration heading. If present, it indicates that this Action is affected by global extension settings and provides a link to the extension configuration page.
How to View all Extensions with Global Settings
To see a list of all extensions in BuildMaster that have global settings, click the Extensions link in the Integration Configuration section of the Administration page:
All extensions in the system are listed; extensions with global settings are hyperlinked. Just click on one of the links to edit the configuration for that extension.
When to Configure
Most of the time, you won’t need to modify the default extension configuration values, as the extensions will attempt to configure themselves appropriately based on whichever server they are executing on. For example, Actions which rely on a specify command-line tool will try to query the system for the installed location of the tool, or if this is not available make a “best guess” based on where it is usually found. Of course, if this auto configuration fails, you will find out about it when you try to execute your build – if this should happen, you may simply manually provide the extension configuration and re-execute.Last modified: 9/26/2013
This content has the following tags: