continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-2068) Build Agent group functionality
Date Sun, 15 Mar 2009 18:35:13 GMT


Wendy Smoak commented on CONTINUUM-2068:

I've just tried this out and have some questions...

It seems that an agent can be added to more than one group.  Is that intended?

What does it mean for a build agent to be in no group(s) at all?

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.

(Except that it does... I see activity in agent-1's logs, but I'll hold off speculating until
I hear how it's intended to work.)

> Build Agent group functionality
> -------------------------------
>                 Key: CONTINUUM-2068
>                 URL:
>             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,
> from  the discussion :
> 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:
For more information on JIRA, see:


View raw message