[
http://jira.codehaus.org/browse/CONTINUUM-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105085
]
Teodoro Cue Jr. commented on CONTINUUM-1387:
--------------------------------------------
After investigating this for a few hours, I've found out that we can actually
do a build even when the project is not yet downloaded. Removing
isInCheckoutQueue( project.getId() ) from buildProject() under DefaultContinuum
does just that. The adverse effect is that some projects are built without
sources. I'm trying to find out how to fix this for now. DefaultBuildController
actually checks if the project is downloaded already or not. It then downloads
the code if it does not exist.
My other concern is the existence of the same project under the checkout queue.
I'm not familiar with the inner workings of the build procedure. Would this
actually download the same source twice if the build procedure downloaded the
source first then the checkout process encounters the same project in the queue?
> Can't initiate a build of a new project in continuum until all modules have
> been checked out
> --------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1387
> URL: http://jira.codehaus.org/browse/CONTINUUM-1387
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1-beta-1
> Reporter: Wendy Smoak
>
> When a multi-module project is added to continuum, a working copy of each
> module is extracted from subversion.
> Typically after adding a project I want to kick off a build.
> If I initiate the build before all the modules are extracted, the ones that
> have not yet been fully extracted will not be queued for build. Only those
> already fully extracted will be built.
--
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
