-
Improvement
-
Resolution: Duplicate
-
Minor
-
None
currently the url is always http://servername/viewvc/ however I need to use http://servername/viewvc.cgi/ which requires me to hack the plugin for a local build. It would be nice to have another box in the advanced section to allow the ability to change viewvc to viewvc.cgi
- duplicates
-
JENKINS-4043 can't link to viewvc installation that doesn't end with "viewvc"
-
- Resolved
-
[JENKINS-5191] make viewvc portion of url configurable
ajpurkiss
added a comment - ViewSVN does not seem to work for me but then it could just be that I need to figure out the complete url as http://servername/viewvc.cgi/ does not work. When I follow a link I get some script errors.
ViewVC take http://servername and your repo name and mangles them together to form something like:
http://servername/viewvc.cgi/?view=rev&root=repo&revision=21029
Now the viewvc.cgi section is hardcoded right now to viewvc and I have to change to to viewvc.cgi for the server I have access to, but after that change it works perfectly. We are trying to get websvn installed which I have been told has a nicer interface but who knows when that will happen.
The simplest fix is to require the viewvc portion added to the server name or the slightly more advanced version clutters up the advanced section with another box. If this is already in wide use then obviously suddenly needing to add viewvc everywhere will break most deploys.
ajpurkiss
added a comment - ViewSVN does not seem to work for me but then it could just be that I need to figure out the complete url as http://servername/viewvc.cgi/ does not work. When I follow a link I get some script errors.
ViewVC take http://servername and your repo name and mangles them together to form something like:
http://servername/viewvc.cgi/?view=rev&root=repo&revision=21029
Now the viewvc.cgi section is hardcoded right now to viewvc and I have to change to to viewvc.cgi for the server I have access to, but after that change it works perfectly. We are trying to get websvn installed which I have been told has a nicer interface but who knows when that will happen.
The simplest fix is to require the viewvc portion added to the server name or the slightly more advanced version clutters up the advanced section with another box. If this is already in wide use then obviously suddenly needing to add viewvc everywhere will break most deploys. 
dvojtise
added a comment - +1
actually, on our forge server the viewvc use an url like http://servername/viewvc.php
the proposed workaround about using ViewSVN partially works, actually, it points to a page that contains a link to the real expected page.
This introduces an additionnal indirection whic doesn't help navigating the sources ...
so being able to configure the url is really useful
dvojtise
added a comment - +1
actually, on our forge server the viewvc use an url like http://servername/viewvc.php
the proposed workaround about using ViewSVN partially works, actually, it points to a page that contains a link to the real expected page.
This introduces an additionnal indirection whic doesn't help navigating the sources ...
so being able to configure the url is really useful In our case, the URL for viewing the repo in a browser is: https://servername/browse/reponame
That page clearly says ViewVC, so I figure this Hudson plugin should apply. 
I have no idea what the URL should be in order to use the ViewVC plugin for Hudson.
Any ideas??
LATER: I made Hudson use ViewSVN for this server+repo with the URL:
https://servername/browse/reponame
and it works fine: revisions, files, diffs all view normally even though the server shows "ViewVC". I'm happy.
Mike
m_broida
added a comment - - edited In our case, the URL for viewing the repo in a browser is: https://servername/browse/reponame
That page clearly says ViewVC, so I figure this Hudson plugin should apply.
I have no idea what the URL should be in order to use the ViewVC plugin for Hudson.
Any ideas??
LATER: I made Hudson use ViewSVN for this server+repo with the URL:
https://servername/browse/reponame
and it works fine: revisions, files, diffs all view normally even though the server shows "ViewVC". I'm happy.
Mike 
Michael Rumpf
added a comment - JENKINS-4043 
as a workaround, can you select ViewSVN instead of ViewVC and enter the URL with viewvc.cgi there? does that work? (I'm not actually sure what viewvc plugin offers.. I've always selected ViewSVN and this seems to work when pointing to ViewVC)