[
http://jira.codehaus.org/browse/CONTINUUM-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-1055:
---------------------------------------
Fix Version/s: Future
> Allow a "suspend/activate" semantic on projects, to except them from
> non-forced builds.
> ----------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1055
> URL: http://jira.codehaus.org/browse/CONTINUUM-1055
> Project: Continuum
> Issue Type: New Feature
> Components: Core system, Database, Project Grouping, Web - UI
> Affects Versions: 1.1-alpha-1
> Reporter: Christian Gruber
> Fix For: Future
>
>
> Currently, if a project is acting up in known ways, there's no way to quiesce
> it until the problem is dealt with. On projects where continuum spams a list
> on purpose, this can be a sort of "false negative" and can cause people who
> can do nothing about the notification to start to stop paying attention.
> It would be nice to allow a project to be in either an active or suspended
> state, with the option for a project admin (not a normal developer) to
> "suspend" the project, so that it will no longer be built. This is highly
> risky functionality, but is helpful during project build structure
> maintenance, for example, so that people aren't spammed with such false
> negative project notifications.
> It would also be good to have this on a project group basis.
--
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
