repository housekeeping for RTC
![]()
All things being equal, a smaller repository is better than a bigger repository, so some "housekeeping" functionality to clean out trash and put things into storage is necessary.
Comments about the following proposals are welcome: 1) 2) 3) 3.1) An archived component is like any other component, except that the contents of the files are not stored in the working repository, but in a secondary repository (e.g. a 2nd Oracle database). Versions, baselines, etc. are all still available in the main repository. 3.2) Anything that requires only the metadata of a component (e.g. showing the component in a stream, displaying baselines) remains exactly as is, except that archived components are marked as archived. 3.3) Anything that requires the actual contents of the files (e.g. load) is obviously not available. 3.4) An archived component can be restored from the secondary repository. The result is that the component is just as it was in the main repository before it was archived. 4) 5) |
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.