Use the .agentupdate command to upgrade an agent to a later version. The
.agentupdate command copies the latest version of the agent executable file
from the Management Console to the Build Forge server.
The name of the agent_executable_file for the Build Forge agent
is required. This file is sent from the Management Console to the Build Forge
server.
For Windows, specify BFagent.exe.
For Unix, specify bfagent.
If you specify the file name only, the .agentupdate command looks for
the executable file in the default installation directory on the Management
Console host:
Use the <directory_path> if you specify a non-default installation
path. Build Forge looks for the executable file in this directory.
Examples
.agentupdate BFagent.exe
.agentupdate bfagent
.agentupdate /usr/lib/bfagent
Prerequisites
For Windows agents, before running .agentupdate, do or note the following:
Verify that the user registered in Server Auth has write permission on <bf-install>\Agent.
On Windows, the BFagent.exe is copied directly to <bf-install>\Agent;
an update directory is not used.
For Unix agents, before running .agentupdate, do or verify the following:
Specify an update directory in the /etc/bfagent.conf file (the default
is the etc directory). In the bfagent.conf file, locate the update_path line,
then specify the full path name, including the executable file name (bfagent).
The .agentupdate command copies the bfagent executable from the Management
Console to the update directory.
Verify that the user registered in Server Auth has write permission on
the update directory.
Upgrading Multiple Agents
To use the .agentupdate command to update the same Build Forge agent on
every Build Forge server on which the agent is installed, use the step Broadcast
property as follows:
Create a selector for the .agentupdate step. The selector defines the
properties for the Build Forge servers whose agents are to be updated.
Set the Broadcast property for the .agentupdate step to Yes.