added a comment - - edited
It seems that an agent can be added to more than one group. Is that intended?
Yes. this was intended to be flexible so that any agent can be assigned to any group.
What does it mean for a build agent to be in no group(s) at all?
As long as it is enabled, build agent with no group can be delegated a build task only from project whose associated "build-environment.build-agent-group" OR "build-environment" is empty.
I'm having trouble with the workflow involved in getting my first distributed build to happen. Now that we have these agent groups, it seems like you can't rely on the default build environment (none selected, just whatever Continuum is running as.) That means that logically, the default build definition, which does not have a build environment selected, will not actually do anything.
i'll check on the latest in the trunk, it ran as I've remembered with the default build definition and 1 enabled build agent (agent is not associated with an agent-group and build env.) setup.
Tried the distributed build in r754817 with minimal configuration and it builds successfully from the build agent.
for reference, here's what i did:
1. added the continuum-buildagent.xml file in continuum-trunk/continuum-buildagent/continuum-buildagent-webapp/target/appserver-base/conf folder
2. jetty:run in continuum-trunk/continuum-buildagent/continuum-buildagent-webapp folder
3. jetty:run in continuum-trunk/continuum-webapp folder
4. enabled distributed build checkbox from configuration page
5. added http://localhost:9191/xmlrpc as a build agent.
6. added a sample project and built it.