[
https://jira.codehaus.org/browse/CONTINUUM-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak closed CONTINUUM-2573.
----------------------------------
Resolution: Incomplete
Fix Version/s: (was: 1.4.2 (Beta))
Marica says it was fixed in 1.4.0 and I've seen it work correctly as well.
Closing as incomplete since I never saw the reported behavior and I'm not sure
exactly when it was fixed. If you can reproduce it in a recent version, please
reopen it with more info.
> Distributed builds are not distributed: they are always scheduled to the last
> agent defined
> -------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2573
> URL: https://jira.codehaus.org/browse/CONTINUUM-2573
> Project: Continuum
> Issue Type: Bug
> Components: Distributed Builds
> Affects Versions: 1.3.6
> Reporter: Paolo Scapin
> Priority: Critical
>
> When more than one agent are available for distributed build, every build is
> queued to the last one defined.
> This way distributed builds are useless.
> The issue is caused by a small bug in class
> org.apache.continuum.builder.distributed.manager.DefaultDistributedBuildManager,
> in method getOverallDistributedBuildQueueByAgentGroup, where the index "idx"
> ios never incremented
> line 916:
> int idx = 0;
> then idx is checked to assign the first queue
> line 932:
> if ( idx == 0 )
> {
> whereToBeQueued = distributedBuildQueue;
> size = agentBuildSize;
> }
> but is never incremented.
> idx should be incremented at line 953, inside the for cycle.
> A similar cycle in the next method (getOverallDistributedBuildQueue) is
> implemented correctly
> Please can anybody insert a fix in the next release?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
