[JIRA] Commented: (CC-939) Add support for hierarchical projects

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

Antoine Levy Lambert commented on CC-939:
-----------------------------------------

I am also interested by nested projects. However in my case there is the added twist that I would like all nested projects to only build when the enclosing project builds. The enclosing project should determine the build order of the nested projects and determine the source control update date. This might in fact be a related but distinct feature. I will also open a separate JIRA issue concerning this idea.

> Add support for hierarchical projects
> -------------------------------------
>
>                 Key: CC-939
>                 URL: http://jira.public.thoughtworks.org/browse/CC-939
>             Project: CruiseControl
>          Issue Type: New Feature
>          Components: Core Application
>    Affects Versions: 2.8.2
>            Reporter: Uri Moszkowicz
>            Priority: Major
>
> CruiseControl should add the ability to support a hierarchy of projects rather than a flat list. A project has its own schedule and checked out version of the repository but often times for these reasons one project is not enough for a real project. You might have schedules that you want to run or just want to test multiple builds in parallel (debug and product builds for example). Right now we rely on naming convention for this purpose but it is hard to order the projects in a meaningful way and the names are rather long.
> The config file would need to be modified to support nested <project> tags. The dashboard would also need to be updated to display a tree of projects which are being built. If the number of projects is small then the tree would be open but if it is large then you might want to collapse it to minimize load on the client (page can be slow due to all the projects). The internal nodes on the tree would be similar to the leaf nodes in that they have an icon showing whether a subproject is currently being built but it should only have two states: busy and free. The other states don't make sense in the conjunctive. The elapsed and remaining time also doesn't make sense. The "all builds" and "all successful builds" links might bring up the union of all nested project builds. The force build butt
 on would apply to all nested projects, as would all other buttons added as a result of CC-935. A new root "projects" project would allow easy control over all projects, as requested in CC-935, such as pausing builds of all projects.

-- 
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

       

------------------------------------------------------------------------------
Forrester recently released a report on the Return on Investment (ROI) of
Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
within 7 months.  Over 3 million businesses have gone Google with Google Apps:
an online email calendar, and document program that's accessible from your 
browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew