...
Continua CI uses multiple repository types when dealing with various VCSs. Each VCS that is supported by Continua has a matching repository type. For example, if you want to link a mercurial repository to Continua then you would have to create a mercurial repository. Each repository type required requires different information to connect to their respective VCS. For more information on a specific type of repository, see the Repository Types section.
...
Depending on the repository scope, repositories can befound be found in different areas of Continua CI:
...
The repositories administration page can be found in the Administration section, under Continous Integration (CI Server). On this page you can edit and delete every repository that exists in Continua CI, regardless of the repository scope.
...
Through this page you can also assign project and global repositories to a specific configuration. Repositories can be assigned by ticking the Repository checkbox in either the Global Repositories table or Project Repositories table (In the figure above, global_source has been assigned to this configuration while binaries has not). Note that when you assign a repository to a configuration that you must click either Complete Wizard or Save & Continue to save your changes.
...
Issue Connectors monitor your commit messages and links any bug fixes to your issue tracking system. Selecting an issue connector on the repository means that continua Continua will monitor all commit messages from this repository for issue ids and then attempt to link these issues to your issue tracking system.
...
The polling frequency can be set to Never (Manual) which means Continua will never automatically check for changes. See the Manually Polling for Changes section below for more details on how to call manual polls.
...
All times are in 24 hour format and are localised to Continua's server time.
Resetting a Repository
Errored Repositories
Disabled Repositories
Manually Polling for Changes
Continua can be instructed to manually poll your repository by calling the Manual Poll Url that is displayed under the Polling Frequency property
Configuration Repositories
The main function of the Configuration Wizard's Repository page is to create and assign repositories to the Configuration. For a repository to be usable by a Configuration it first must be assign to it. Global and Project Repositories can be assigned to a Configuration by selecting the checkbox next to the Repositories name. The following picture shows all the repositories in Continua CI that this Configuration can access. Both the Global Repository MyGlobalRepo and the project level repository myProjectRepo are assigned to the Configuration we're editing since its check box is ticked.
Note: The two Configuration specific repositories MyConfigurationRepo and hg do not have a check box next to its name. This is because Repositories with Configuration scope are always assigned to the Configuration.
Creating Repositories in the Configuration Wizard
A repository can be created both in the Project Wizard and the Configuration Wizard. The Project Wizard restricts you to creating and modifying repositories at the Global and Project level scope. In the Configuration Wizard, you have a third option when creating a Repository, and that is to create one within the Configuration scope. A repository created with Configuration scope can only be accessed by that Configuration and is automatically assigned to the Configuration.
Project Repositories
The Repository step of the Project Wizard allows you to create repositories that can be used by any Configuration in Continua (known as global repositories) and repositories specific to the current project (known as project repositories) which can only be used by Configurations in the project.
The repositories are displayed grouped by their scope type, Global and Project.
Each section has its own
| Makeitblue |
|---|
[Create] |
| Makeitblue |
|---|
[Create] |
Issue Tracker
If you've setup an Issue Connector, this is the place to assign it to the repository. The Issue tracker is optional and can be added at any time. See Issue Connectors for more information.
Polling Frequency
The frequency at which Continua will check for changes in the repository.
Type
The type of version control system of your repository. See Repository Types for a full list of supported repositories. When you select a repository type, additional tabs will be displayed containing repository specific settings.
Validation
Once a Type has been selected and the appropriate fields filled in, you can click the Validate button to check if the settings are correct.
Modify a Repository
After creating a repository you will see it listed on the wizard's repository page.
Resetting a repository forces Continua to delete the local repository cache for the specified repository and pull the latest changesets from your repository. When a repository is reset, Continua will get the latest changeset for each branch in that repository.
If your repository is in an errored state then resetting it may fix the issue.
Repositories can be reset through the Administration Repositories page.
Errored Repositories
A repository will be in an errored state if there are any issues when Continua attempts to get the latest changesets. If a repository is in an errored state then you can try to resolve the issue through the Administration Repositories page. Resolving a repository will reinitialise it and force to get the latest changesets. If you resolve a repository and it is still in an errored state, then you may need to reset the repository.
If resolving and resetting does not fix your repository then you should check your repository settings.
Disabled Repositories
By disabling a repository you are telling Continua to stop interacting with it. If a repository is disabled then Continua will not check for new changesets and any references to that repository will fail during the build process. For example, if you reference a disabled repository's path by using the following syntax $Source.myRepo.Path$, then at build time this will not be resolved, resulting in a failed build. As far as the build engine is concerned, the repository doesn't exist which means it cannot get the path value from the repository.
Manually Polling for Changes
Continua can be instructed to manually poll your repository by calling the Manual Poll Url that is displayed under the Polling Frequency property. Note that the Manual Poll Url property will only be displayed if Polling Frequency is set to Never (Manual).
Each repository will list its name, repository type and issue tracker. In addition, it will show which configurations are using the repository and if you have the right permission, the links to edit, delete and change the scope of a repository. Editing a repository will popup a dialog exactly like the one used to create it. Changing a repositories scope is as simple as clicking the link. Note however, you will not be able to change the scope of a repository until it's safe to do so. For example, if you have a global repository that is used by configurations in ProjectA and ProjectB then you can't change the scope of that repository to exist only in ProjectA since configurations in ProjectB would then lose access to it.