[
http://jira.codehaus.org/browse/CONTINUUM-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169731#action_169731
]
jan ancajas edited comment on CONTINUUM-2068 at 3/16/09 2:26 AM:
-----------------------------------------------------------------
{quote}
It seems that an agent can be added to more than one group. Is that intended?
{quote}
Yes. this was intended to be flexible so that any agent can be assigned to any
group.
{quote}
What does it mean for a build agent to be in no group(s) at all?
{quote}
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.
{quote}
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.
{quote}
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.
*Update*
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.
was (Author: jancajas):
{quote}
It seems that an agent can be added to more than one group. Is that intended?
{quote}
Yes. this was intended to be flexible so that any agent can be assigned to any
group.
{quote}
What does it mean for a build agent to be in no group(s) at all?
{quote}
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.
{quote}
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.
{quote}
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.
> 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
