Murali Mohan created CONTINUUM-2706:
---------------------------------------
Summary: Should we stop from queueing projects if another bulid is
being executed?
Key: CONTINUUM-2706
URL: https://jira.codehaus.org/browse/CONTINUUM-2706
Project: Continuum
Issue Type: Wish
Affects Versions: 1.4.1
Environment: Ubuntu, tomcat
Reporter: Murali Mohan
Priority: Minor
Problem and the argument
========================
It is difficult to balance the schedules when there are multiple projects
running in Continuum.
One reason is that we cannot queue up builds from the same project is one is
already being executed. This is not needed in my opinion. The reason for having
a queue is to avoid these things. Let the build be queues and let it execut
after the current one is done. What is wrong with it?
Because of this restriction, we have to sometimes plan the schedule so that it
executes only after the any other projects having completed execution. This is
a pain as we cannot predict when a build will complete simply because we cannot
know when it will start to execute as there is a queue and there can be many
builds in front.
Java code:
==========
CreateBuildProjectTaskAction.java:
This is the snippet where this occurs:
if ( executor.isBuilding( project ) || project.getState() ==
ContinuumProjectState.UPDATING )
{
// project is building
getLogger().info( "Project '" + project.getName() + "' already being
built." );
continue;
}
Question
=========
Can we change it to this (we will continue with build process even if another
one is being executed):
if ( project.getState() == ContinuumProjectState.UPDATING )
{
// project is building
getLogger().info( "Project '" + project.getName() + "' already being
built." );
continue;
}
--
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
