[CONTINUUM-509] Ability to process scheduled builds the same as forced builds.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.2
• Component/s: Core system
• Labels: backlog-to-cleanup
• Assignee: Unassigned
• Reporter: Shinobu Kawai
• Created: 12/Dec/05 14:49
• Updated: 20/Nov/12 01:09

Description

It would be great if you could configure a build schedule to act like a forced build on the scheduled build.

The use case for this is when you have two build definitions:

• One will be set to default for a forced, light build. For example, install the artifact.
• Another will be set to a scheduled, heavy build. For example, deploy the artifact and the project site.

If the default build is triggered, the other build will be skipped since nothing has been updated since the forced build. And we do not want to do heavy stuff in the default build.

Issue Links

• is duplicated by: CONTINUUM-379 Build from fresh checkout option
• is duplicated by: CONTINUUM-568 Need to be able to schedule forced builds
• is duplicated by: CONTINUUM-685 Make builds optionally build even when there are no changes
• is related to: CONTINUUM-1507 Build are always done when it exists several build definitions for the same project group
• is related to: CONTINUUM-1724 Queue build definitions separately
• relates to: CONTINUUM-686 Provide each build definition for a given project with its own checked-out workspace.