[
https://issues.jenkins-ci.org/browse/JENKINS-11887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158927#comment-158927
]
Rob Guttman commented on JENKINS-11887:
---------------------------------------
Our Trac setup is for multiple git repositories. And so the repo name must be
included in the browser url. More details can be found here:
http://trac.edgewall.org/wiki/0.12/TracRepositoryAdmin
However, there is one exception to this which is a partial workaround. You can
alias the default (i.e., nameless) path to go to a single git repo. This
should mostly work for us as we have one main git repo that we care about most
for jenkins. But this would just be a workaround for this special case. Full
multi-repo support would be better.
> Support Git for "Repository browser" setting
> --------------------------------------------
>
> Key: JENKINS-11887
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11887
> Project: Jenkins
> Issue Type: Improvement
> Components: git, trac
> Environment: Jenkins 1.441, Trac Plugin 1.12
> Reporter: Gerd Zanker
> Assignee: Gerd Zanker
> Priority: Minor
> Labels: git, trac
> Fix For: current
>
>
> In the [Trac Plugin
> documentation|https://wiki.jenkins-ci.org/display/jenkins/Trac+Plugin] the
> configuration is described as
> bq. In the Source Code Management section, choose "Trac" for the "Repository
> browser" setting.
> This settings "Trac" is not available for when I use git as a SCM.
> Can this selection be added?
> ----
> The Trac-plugin code supports "TracGit" for the "Repository browser" setting.
> The given Trac URL at the top of the job settings will be used to generate
> links for git changesets, files and diffs to your Trac "Browse Source" area.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
