[
http://jira.codehaus.org/browse/CONTINUUM-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105376
]
Jesse McConnell commented on CONTINUUM-1387:
--------------------------------------------
if there is an easy way to block the build queuing process until continuum has
had a change to fully initialize upon adding the project, I would prefer that
solution personally..
new queuing structures smell like new features to me and we are in beta for 1.1
:)
but thats just my opinion.
the build process will checkout on an empty project directory, that is how the
'Build Fresh' feature works, it smokes the stuff in that directory and then the
build process just checks it back out.
odds are you would be ok just removing that checkout queue check like you were
thinking of...could you maybe on the build check if it is in the checkout queue
and if it is wack it out of there and then add into the build queue since we
know the build process will check it out anyway?
> 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
> Assignee: Teodoro Cue Jr.
>
> 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
