[
http://jira.codehaus.org/browse/CONTINUUM-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jan ancajas updated CONTINUUM-2068:
-----------------------------------
Attachment: CONTINUUM-2068-3.patch
added patch again.
- fixed selection of agents algorithm.
- added an overall task-queue-executor for distributed build queue to delegate
the task.
- implemented a 1 queue 1 executor approach for every build agent
- for the scenario where the current task in the distributed build queue
doesn't have a matching build agent (e.g. build agent of that particular group
is disabled ), i'll just add back the task at the end of the queue so as not to
block the other tasks in line. in this way, when the matching build agent is
found in the future, the task will be processed.
- rule of selecting the build agent in the group : it will return the first
non-busy agent from the group , else it will return the first agent in the
group.
- refactors:
move DistributedBuildTaskExecutor, DistributedBuildTaskQueueExecutor to
continuum-api.
> 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
> Attachments: CONTINUUM-2068-2.patch, CONTINUUM-2068-3.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
