[#CIB-651] Allow the master agent to be disabled/enabled

Pulse

Allow the master agent to be disabled/enabled

Created: 06/Oct/06 04:37 PM Updated: 18/Oct/06 02:57 PM

Component/s:

Agent

Affects Version/s:

1.1.13

Fix Version/s:

1.2

Description

« Hide

For some, having an agent in the web app is convenient, but it would also be convenient to not allow the usage of the agent in the pulse ui. We have one server that acts as an central point for our web UI's (Pulse, Jira, Confluence, Fisheye, etc). This box is not intended to run builds as it merely processes http request to the real boxes. We would like to disable the agent in the Pulse ui and only use agents installed on other machines properly outfitted for building software.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Binyan - 06/Oct/06 07:11 PM

A side note on this issue is that if an end user does disable the agent in the UI then it should not contribute to the # of agents you are licensed for. Instead the license should maybe refer to the number of active agents to calculate whether a user is above their license level or not.

[ Permlink | « Hide ]

Daniel Ostermeier - 18/Oct/06 11:20 AM

The licensing for agents is there to limit the number of remote agents. The master agent is there as a complimentary agent to allow building on the pulse server. Whilst it is implemented as an agent, disabling it will not add one available agent back to the agent license pool.

[ Permlink | « Hide ]

Daniel Ostermeier - 18/Oct/06 02:57 PM

Resolved in svn revision 2297.

Enabling and disabling has no impact on the available license pool for remote agents since, by definition, the Server is not a remote agent.