[CONTINUUM-2457] A successful build should not be required in order to release.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.3.5 (Beta)
• Component/s: Release
• Labels: backlog-to-cleanup
• Assignee: Unassigned
• Reporter: Wendy Smoak
• Created: 03/Feb/10 08:56
• Updated: 20/Nov/12 01:09

Description

As discussed on the dev list, the success of a build at some point in the past is not related to the success of a release now.

See http://old.nabble.com/Re%3A-Thoughts-on-build-environment-selection-when-releasing-in--distributed-build-setup-p27430431.html

The restriction to have the projects in 'build success' state before it will let you do a release should be dropped.

I should be able to add a project and immediately release it, or release a group in which one or more of the projects has a error or warning.

The release may fail, but I should not be prevented from starting it.

Issue Links

• relates to: CONTINUUM-2458 Continuum Release should do a checkout if there is no working copy