Adding a New Remote Server to an Existing BuildMaster Installation
Orchestrating remote servers are an integral part of BuildMaster’s automated deployment mechanism. A server becomes recognized or registered with BuildMaster once the agent software has been installed on it, and a reference to the agent’s URL is added from within the BuildMaster software itself.
To begin the installation process for an agent, select External Servers from the Administration page:
This takes you to the Server Overview page, where you can add servers or server groups to BuildMaster.
Depending on the operating system of the remote server, you must download the appropriate agent. If you select Download Windows Agent, you will see the instructions:
Windows Agent Prerequisites
- Windows XP/2003/2008/Vista/7
- .NET Framework 2.0 with IIS or .NET Framework 3.5 without IIS
- Port accessible from the BuildMaster server via HTTP
Installation Instructions
- Download the Agent Installer on the remote server.
- Run the installer on the remote server with a user account with local administrator privileges.
- Complete the Agent Installation wizard.
Adding the Server to BuildMaster
- Add the server to BuildMaster using its name/address and port configured in the installer.
- If BuildMaster cannot access the server, verify that a firewall is not blocking the specified port.
If you choose Download Linux Agent you will see:
Linux Agent Prerequisites
- Apache with mod_mono
- Port accessible from the BuildMaster server via HTTP
Installation Instructions
- Download the Agent on the remote server.
- Visit inedo.com/support/documentation/topics/installation/agent-linux.
Adding the Server to BuildMaster
- Add the server to BuildMaster using its name/address and port configured in the installer.
- If BuildMaster cannot access the server, verify that a firewall is not blocking the specified port.
Once you have followed the appropriate steps for the remote server’s OS, you can select Add New Server on the Server Overview page:
The Server Name can be anything descriptive, it is meant to be a friendly name for the lists and dropdowns in BuildMaster. The Agent Address is a URL that points to the agent service; in my case I’ve chosen the hostname of the integration server (buildmasterint) on port 83 (which is specified when the agent is actually installed on the server). When you choose Save, you’ll be taken to the Server Details page where you’ll be shown which extensions are installed on the server along with any environments it may be associated with.
Last modified: 5/15/2012
Related Content
Haven't found what you're looking for? Try some of the content below.
Knowledge Base Articles
Last Updated: 5/10/2012There are two versions of the BuildMaster Windows Agent:
IIS hosted: Functions as an ASP.NET web application hosted with IIS WCF hosted: Runs as a standard Windows service and requires .NET 3.5
In a...
Last Updated: 11/26/2012Overview
The TCP-based agent runs as a Windows service on a remote server and allows BuildMaster to connect to it and proxy build actions through it in a similar manner to the previous SOAP agents. T...
Last Updated: 10/31/2012
For BuildMaster to orchestrate a remote server, an Agent is required. Currently,
BuildMaster has four types of agents:
Local Agent
This agent is actually part of the BuildMaster servic...
Documentation
Tutorials
Support Questions
Pull-based agent -
We are trying out BuildMaster, due to the nature of our Network Architecture, we are dealing with a few firewalls that prevent us from using a Push Ap...
Agent alternatives -
The BuildMaster agents are required in order to add servers to the configuration. I'm in a position where I'm not authorized to install any software o...
This content has the following tags:
buildmasteragents
