As explained on the Repositories & Triggers page, a repository in Continua is a reference to an external version control system. Once a Continua Repository has been created you can connect it to a Configuration and then use/access the files in that Repository within your build process. Continua will also monitor that repository for changes and trigger builds off it if you have setup a Trigger. Since Continua allows you to create many projects and many Configurations within each project, the list of repositories could grow quite large. To reduce the potential amount of clutter and make repositories easier for the user to manage and secure, we allow Repositories to have one of three scopes. They are Global, Project and Configuration.
Note: All Repositories created in Continua are created equally and work the same way regardless of their scope. The scope of a Repository is simply a way to reduce the amount of Configurations or Users that can see it. The scope of a Repository can always be changed.
Repositories with Global Scope
Global Repositories are accessible anywhere in Continua and can be connected to any and every Configuration.
Repositories Project with Scope
Project Repositories are only accessible by Configurations belonging to that Project. By creating a Repository with Project scope, you can lock Users out of the project which will in turn disallow them from seeing the Repositories within it.
Repositories Configuration with Scope
Configuration Repositories are only accessible by a single Configuration. Creating a Repository with Configuration scope has the same security benefits as Repositories with Project scope but at a Configuration level.
Changing a Repositories' Scope
At any point in time you will be able to change the scope of a repositories. Obviously widening the scope is safer than narrowing but either way is possible. By widening the scope of a Repository, for example, making a Project repository Global or a Configuration Repository Project or Global you open it up for many more Configurations to use it. Conversely, narrowing the scope of a Repository lessens the amount of Configurations that can use it. Therefore, when narrowing the scope of a Repository (moving a Global to Project or Configuration scope, or a Project Repository to Configuration scope) you must take care that Configurations that use it still can after changing the scope.
Note: Continua will notify and stop the user from narrowing the scope of a Repository if it means a Configuration that currently uses it will no longer be able to use it if the scope change went ahead.