BuildMaster Documentation


The BuildMaster Service is key component of BuildMaster's architecture, and is what actually runs your deployment plans using the execution engine. It's a standard Windows Service Application, and may be managed and configured using the Windows Service Manager or sc.exe as you see fit.

Managing the Service from the Web Application

In addition to stopping and starting the Otter Service, you can see the service's live logs; this may be helpful when diagnosing problems or working with Inedo's support team to track down unexpected behavior or bugs.

BuildMaster  Administration Services

You can also manually trigger the task runners that the service would otherwise routinely execute. This should only be needed in debugging purposes, as the Web Application will trigger them in response to certain actions (such as editing a plan), and they are always executed on service start.

  • ScheduleExecuter
  • AgentUpdater
  • PlanActionExecuter
  • ExtensionUpdateExecuter
  • ScmTriggerExecuter
  • EventListenerExecuter
  • PromotionRequirementVerifierExecuter
  • ScheduledPromotionExecuter
  • RetentionPolicyExecuter
  • IssueTrackerSyncExecuter

BuildMaster Service Configuration

By default, the BuildMaster Service is named INEDOBMSVC, runs under the NetworkService account, and is granted Read, Write, ListDirectory privileges to the following paths:

  • ExecutionTempPath
  • ExtensionsPath
  • ExtensionsTempPath

If you choose to configure this as a custom domain account, it will be important to grant these same privileges.