continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-1724) Queue build definitions separately
Date Wed, 22 Apr 2009 14:47:44 GMT


Brett Porter updated CONTINUUM-1724:

    Fix Version/s: 1.x
          Summary: Queue build definitions separately  (was: Queue builds while building)

I think we need to look at making build definitions a first class citizen - or some kind of
equivalent - so that they can be separately scheduled, operate on their own checkout, etc.

> Queue build definitions separately
> ----------------------------------
>                 Key: CONTINUUM-1724
>                 URL:
>             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
> 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:
For more information on JIRA, see:


View raw message