Adding repository browsers to the SCM is useful if there are web based repository browsers that can display more information about the change set or the SCM in general. Examples of repository browsers are FishEye, viewvc and sventon.
Create a class, that extends RepositoryBrowser<ChangeLogSet.Entry> for your SCM that will act as the base class for each repository browser implementation. The abstract method is getChangeSetLink() that returns an URL. But if your repository browser can show other information, such as difference of a file between change sets or the file itself, then you should add abstract methods in your repository browser class.
Add a field for storing the repository browser.
The configuration of the SCM class must also be updated to support the new repository browser. The constructor must set the repository browser responsible for the SCM and the newInstance() method must be overridden to retrieve which repository browser to use.
Add the following section to the config.jelly that is used for configuring the SCM.
The index jelly for the ChangeLogSet must be updated to include the links to the repository browser.
Adding a repository browser to the SCM, is simple by adding two files, the class extending the RepositoryBrowser class and the jelly file for configuring it.
The repository browser must be configured with the base URL, so it can be used when determining the URL to link the change set to. The jelly files goes into src/main/resources/hudson/plugins/[SCM]/browsers/CodePlexTfsBrowser folder.
Skip to end of metadata Go to start of metadata