[ 
https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322129#comment-322129
 ] 

Murali Mohan commented on CONTINUUM-2704:
-----------------------------------------

So I have made the change (removed the synchronize keyword) in the code I got 
for version 1.3.6 (from the corresponding branch). I couldn't get the trunk 
code to work which is explained here - 
http://jira.codehaus.org/browse/CONTINUUM-2705

And this 1.3.6 version has been running and executing all our builds for more 
than a week now. It is much faster and I am seeing less problems now. 
Initially, I used to have a load of problems because of builds not getting 
completed on time as the shell builds were blocking each other. Not any more.

So works well for me in 1.3.6


                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run 
> in different queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute 
> the build until the shell build from B is complete. it is almost  like A is 
> waiting for B to finish. Please note that maven builds are happily running in 
> parallel in these 2 queues. It is only the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B 
> from Continuum and ran the shell script for A from command line and it worked 
> fine - both ran in parallel. So, I think Continuum has a bottle neck 
> somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to