[
http://jira.codehaus.org/browse/CONTINUUM-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169747#action_169747
]
Wendy Smoak commented on CONTINUUM-2068:
----------------------------------------
> 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.
So that means groups are optional. You can add a bunch of agents, not put them
in any group, and it should work out of the box with the default build
definition [no build env, therefore no agent group]. This would explain why I
was seeing activity on my build agent, which wasn't in a group.
Thanks for the explanation!
> Build Agent group functionality
> -------------------------------
>
> Key: CONTINUUM-2068
> URL: http://jira.codehaus.org/browse/CONTINUUM-2068
> Project: Continuum
> Issue Type: New Feature
> Components: Distributed Builds
> Reporter: jan ancajas
> Assignee: Maria Catherine Tan
> Fix For: 1.3.2
>
> Attachments: CONTINUUM-2068-2.patch, CONTINUUM-2068-3.patch,
> CONTINUUM-2068-4.patch, CONTINUUM-2068.patch
>
>
> from the discussion :
> http://www.nabble.com/Missing-Functionalities-in-Distributed-Builds-td21697552.html
> We can have the user select which agent to add in a group and have that
> group attached to a build environment? So instead of agent attached to a
> build environment, it will be group of agents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
