I think it's a good direction for the build agent to be specifying more of its own information rather than the master trying to tell it who it is.
However, I'd go with deriving the data rather than asking the user to specify it - otherwise you could get small inconsistencies creep in. In the utils libraries there is an Os class that can send back the full OS name, or just the family. These might help the master make decisions on how to group them without putting any burden on the agent to decide / configure anything. - Brett On 07/12/2010, at 4:45 PM, Mark John Kennedy Magallanes wrote: > hi all, > > I'm proposing to add a String field to the BuildAgentConfiguration model used > in by the continuum > master to save build agents. Right now BuildAgentConfiguration has the > following fields String url, > String description, boolean enabled, I'm suggesting to add another field > String platform so that > the continuum master could keep track of the platform of the registered build > agents in the continuum > master. This will in a way lessen the task when you want to know the > available platforms of the build > agents registered in the continuum master since it will also be recorded in > the continuum.xml rather > than reading each registered build agents to know it's platform. > > any feedback to my proposal? or any other suggestions? > > > Thanks, > > Mark Magallanes > > -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
