Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316731 - Separate repository and provider
Summary: Separate repository and provider
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 04:47 EDT by Thomas Hallgren CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Hallgren CLA 2010-06-14 04:47:12 EDT
The current RMAP Provider is the placeholder for all information related to a SCM repository. Consequently, if several providers are used for different sub trees found in that repository, this information needs to be repeated several times.

At present, discovery is performed by requesting specific files from the remote provider in order to determine the best fit. In most cases, the best fit is whatever is found at one location such as head of the current branch, head of main, a specific revision of a branch etc. In such cases it would often be much faster to check out a whole sub tree and then perform the discovery on the local disc. This would also make integration with a CI system like Hudson a lot simpler. The CI system can discover that a subtree has changed and automatically start a new build with an updated tree.

In b3, we now introduce the concept of 'repositories'. A repository is a complete definition of a repository with connection credentials, branch points, and policies. A provider can then reference such a repository using an ID. We need this in Buckminster too.