BuildMaster was designed to be extensible and adapt to virtually any
third-party tool needed. Although BuildMaster ships with a number of common
extensions (and Inedo can develop extensions by request), users are welcome to
develop their own extensions to fit their specific needs.
The following are, at a high-level, the extensible features of BuildMaster.
These are documented in more detail in the API and BuildMaster SDK.
- Action – an action can programmatically interface with nearly any
third-party tool; generally, actions are built to wrap a command line
utility or to perform unique tasks not covered by existing actions.
- Unit Test Action – a special type of action that records test
against the build from a unit testing framework such as NUnit.
- Provider-Based Action – a special type of action that is designed
to work with providers (Database, Source Control, Etc); this sub-type of
action simplifies creation and association of actions with providers.
- Database - interface to a database engine.
- Source Control - interface to a source control management system.
- Issue Tracking - interface to a bug-or-issue-tracking system.
- Directory - interface to a user and group store.
- Predicates - used by action groups to control execution.
- Notifiers - executed when events occur to notify users.
- Configurers - allows extensions to be configured at a central
- Triggers - executed when events occur to perform some kind of
- Promotion Requirements - used to determine if promotion to a
specific environment is allowed.
This content has the following tags: