[CONTINUUM-1724] Queue build definitions separately

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.1
• Labels: backlog-to-cleanup
• Assignee: Unassigned
• Reporter: Matt Kern
• Created: 11/Apr/08 05:32
• Updated: 20/Nov/12 01:09

Description

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.

Issue Links

• relates to: CONTINUUM-1507 Build are always done when it exists several build definitions for the same project group
• relates to: CONTINUUM-686 Provide each build definition for a given project with its own checked-out workspace.
• relates to: CONTINUUM-509 Ability to process scheduled builds the same as forced builds.
• relates to: CONTINUUM-564 Change focus of build from projects to Build Definitions