[JIRA] Commented: (CC-774) An optional attribute count to element <veto> should be added.

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown [JIRA] Commented: (CC-774) An optional attribute count to element <veto> should be added.

by JIRA jira@users.public.thoughtworks.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ http://jira.public.thoughtworks.org/browse/CC-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_16552 ]

Jeffrey Fredrick commented on CC-774:
-------------------------------------

This is an interesting idea.  I think the way I would approach it would be for a maximum # of days since the last build rather than trying to keep a count.

> An optional attribute count to element <veto> should be added.
> --------------------------------------------------------------
>
>                 Key: CC-774
>                 URL: http://jira.public.thoughtworks.org/browse/CC-774
>             Project: CruiseControl
>          Issue Type: Improvement
>          Components: Core Application
>    Affects Versions: 2.7.1
>            Reporter: Vocht
>
> The  pure concept of continuous building  does not allow a element as <veto>, because it is possible that a project is not build for a long time because the project, which is used in an element <veto>, is very dynamic and never up-to-date at the time of building.
> Of course in practical use you does not want to a project, which is very time-consuming, to be rebuild if another project is not up-to-date.
> Therefore i find it excellent to have the new element <veto> in order to optimize the building of time-consuming projects.
> But an unlimited veto breaks the concept of continuous building  completely.
> From my point of view a good compromise between the concept's needs and the practical requirements would be having a veto which is limited.
> I would like to have the following improvement:
> 1. An optional attribute "count" should be added to the element <veto>. Please understanding the attribute name as a working name.
> 2. This attribute gives the maximum number the veto is allowed to stop a build. If it is reached , this veto should be ignored.
> 3. Two or more element <veto> should be handled independently.
> 4. After a successful build the counter for the number of each element <veto> are set to zero.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Cruisecontrol-devel mailing list
Cruisecontrol-devel@...
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel
LightInTheBox - Buy quality products at wholesale price!