...
When Continua gets the latest changesets from your source repository, it automatically retrieves all commit/checkin messages associated with that changeset. If your source repository is linked to an issue connector then it will also try to parse the commit/checkin messages for issue idsIds. It will then take those issue id's Ids from the commit message and generate a hyperlink to that issue in your issue tracking system. The list of hyperlinks will be displayed in the "Issues" tab when viewing a build. Issue Connectors do not interact with your issue tracking system, they just generate hyperlinks to it! It won't open or close issues or require any kind of login to your system.
...
Lets say you have set up a Repository Trigger so every time a check in is made, the configuration is built. Every time a configuration is built, the build always knows about the latest changeset, or in this case, the changeset that triggered the build. If your company's policy is to have meaningful commit messages that reference your issue tracking system, then an Issue Connector will link Continua to it. With an Issue Connector, you can give it a regular expression to retrieve the issue id Id and other information from the commit/checkin message and use this information to create hyperlinks to a specific issue.
...
The Commit Message Regex is a regular expression that tells the issue connector to extract certain data out of commit messages. Any information that should be extracted MUST be placed into a named group. Named groups have the following syntax <namedGroup>. For example, to extract an issue idId, you could use the following regex: #(?<id>\d+). This regex gets any number that is preceded by a # (hash) symbol and saves the value into the <id> named group.
...
The Issue Server URL is a template URL for generating links to your issue system. It allows you to dynamically set the value of the URL based on specific build information. Any information that is pulled out of a commit message using named groups (read above) can be inserted into the URL. All of the default issue connectors simply pull out the issue id Id by using the <id> named group in the Commit Message Regex and insert the id Id field into the generated issue url by using the {id} syntax (See the example provided in the 'Why Use an Issue Connector?' section).
...
Issue Connectors also allow for certain repository information to be included within the Issue Server URL. The following tags can be used:
| Tag | Description | Url and Value | Example |
|---|---|---|---|
| {repo.url} | Extracts the source url from the repository and places it in the Issue Server URL | Repository Source URL: https://github.com/username/testGitHub.git {repo.url}: https://github.com/username/testGitHub | Issue Server URL: {repo.url}/issues/{id} Generated Link: https://github.com/username/testGitHub/issues/1 |
| {repo.subdomain} | Extracts the subdomain from the repository source url and place it in the Issue Server URL | Repository Source URL: https://myrepo.kilnhg.com/Code/Repositories/Group/Test1 {repo.subdomain}: myrepo | Issue Server URL: http://{repo.subdomain}.fogbugz.com/default.asp?{id} Generated Link: http://myrepo.fogbugz.com/default.asp?1 |
| {repo.host} | Extracts the host from the repository source url | Repository Source URL: https://myrepo.kilnhg.com/Code/Repositories/Group/Test1 {repo.host}: myrepo.kilnhg.com | Issue Server URL: http://{repo.host}/default.asp?{id} Generated Link: http://myrepo.kilnhg.com/default.asp?1 |
| {repo.path} | Extracts the path and query from the repository source url | Repository Source URL: https://git01.codeplex.com/mygitrepo {repo.path}: mygitrepo | Issue Server URL: http://{repo.path}.codeplex.com/workitem/{id} Generated Link: https://mygitrepo.codeplex.com/workitem/1 |
Validation
Once you have given the Commit Message Regex and the Issue Server URL a value, you can validate your settings by providing a typical commit message you would use when checking in a fix for a bug. If the validation was successful, a link will be generated that points to your issue tracker.
...
Generated URL: http://www.issues.com/myawesomeproject/issue/29981
Named Groups can appear multiple times in the Issue Server URL
...
Generated URL: http://myawesomeproject.issues.com/myawesomeproject/issue/29981
Multiple Issue Ids in a commit message produce multiple Issue links
...