[
http://jira.codehaus.org/browse/CONTINUUM-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173959#action_173959
]
Matt Kern commented on CONTINUUM-1724:
--------------------------------------
It is useful for build definitions to share one checkout.
e.g. I have a number of huge shell project checkouts (approaching 1GB). Within
each project there are a number of build definitions which share the checkout.
I could split the build definitions into separate projects right now, but that
would require multiple huge checkouts, considerably slowing the refresh/update
cycle.
> Queue build definitions separately
> ----------------------------------
>
> Key: CONTINUUM-1724
> URL: http://jira.codehaus.org/browse/CONTINUUM-1724
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Matt Kern
> Fix For: 1.x
>
>
> I have a project with a couple of build definitions:
> (a) build source files into a tarball deployable by developers;
> (b) build installer from most recent tarball.
> Build definition (a) runs pretty much constantly because people are regularly
> committing changes.
> Build definition (b) runs nightly. I also want to be able to run (b) by
> clicking the build definition "Build" button. I would expect this to add (b)
> to the build queue. It doesn't because (a) is building. Why should what (a)
> is doing have any bearing on whether (b) can be queued?
> I can't easily split (a) and (b) into separate projects because they share a
> number of files. The only other workaround is to disable (a)'s schedule,
> wait for it to complete, queue (b) and then renable (a)'s schedule -- irksome.
--
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
