![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Build Manager Project Groupings - not all grouping shown Topic Summary: bug or feature? Created On: 15-Apr-2005 14:38 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
The default "Build Manager Project Groupings" does not show ALL Project Groupings. When I first did not see a Grouping for each active release, I thought there was a bug. But, after a quick survey, it seems to show Groupings only for release/purpose pairs for which there is a corresponding modifiable project version. Is this correct? If so, this should be stated more clearly in the help documentation. (The documentation does say that it shows "current build management projects", but without defining "current".)
|
|
![]() |
|
![]() |
|
Yes that's correct. The project explorer shows projects so if a query for project groupings returns no projects, we too the design decision that it would lead to a lot of visual clutter showing an empty project grouping. In most cases, when a project grouping becomes empty, it is automatically deleted anyway. This is done to reduce the need for manual maintenance. Hope that helps. David.
|
|
![]() |
|
![]() |
|
A small update: Although we automatically deleted empty project groupings in the beta release, we've removed that feature in the general release. It turned out to be too expensive to find the project grouping and check whether the project grouping was empty, every time a project was deleted, or had its release or purpose change. A user can easily create a rule, using the Save Offline and Delete facility, to periodically delete empty project groupings, if he chooses to do so.
|
|
![]() |
|
![]() |
|
If the idea is to "reduce the need for manual maintenance" (which is a great idea!), then why back off from doing it all of the time (e.g. when a project is deleted or modified) to doing nothing? Why not make part of the tool what you are purposing users do manually. Have the tool automatically (configured?) delete the project groupings on a schudule (daily?).
Of course, there are a lot of areas where built in maintenance scheduled would be nice, but why not start here. :-) |
|
![]() |
|
![]() |
|
The Save Offline and Delete feature provides a facility for deleting objects according to a set of user-configurable rules, and it can be scheduled, using a standard scheduling application. Since both UNIX and Windows provide standard well-known scheduling facilities, we didn't feel it was our place to introduce our own scheduling facility, which we believe would be beyond the scope of a Configuration Management tool.
It would be a good idea to provide an out of the box SOAD rule for deleting empty project groupings, and we have an enhancement request for consideration for a future release for such a rule (R#21682). |
|
![]() |
|
![]() |
|
Todd, a correction on my earlier reply. The "Build Manager Project Groupings" query does query for project grouping objects. If the query is not showing a project grouping, then either that project grouping does not exist, or its properties do not match the query. Note that if this was on an upgraded database, we do not necessarily create a project grouping for every project. Troy will email you separately about this. It's possible, therefore, that this issue is that you have projects in an upgraded database and the fact that you don't see a project grouping in the explorer is that they do not have a project grouping in the database. You can check this from the CLI by querying for the project, and then using the ccm relate -show -from command. If the project has a project grouping there will be a relation named project_in_pg running from the project grouping object to the project.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.