MantisBT - CDash
View Issue Details
0009120CDashpublic2009-06-08 17:482010-02-21 12:33
Torsten Rohlfing 
Julien Jomier 
normalmajoralways
closedfixed 
1.4 
1.5 
0009120: CDash generates wrong diff URLs for ViewVC (at least on NITRC.org)
Using CDash 1.4.2 from svn, I am having trouble getting CDash to generate diff URLs for a ViewVC 1.0.0 server run at NITRC.org.

CDash generates a URL like

http://www.nitrc.org/plugins/scmsvn/viewcvs.php/?root=cmtk/?action=browse&path=/CHANGELOG&r1=34&r2=35 [^]

when ViewVC would like this:

http://www.nitrc.org/plugins/scmsvn/viewcvs.php/trunk/core/CHANGELOG?root=cmtk&r1=32&r2=35 [^]

There does not seem to be a way to configure CDash to provide the second form.

The dashboard for these examples is run at

https://neuro.sri.com/CDash/index.php?project=CMTK [^]

and is configured to use ViewVC with entry URL

www.nitrc.org/plugins/scmsvn/viewcvs.php/?root=cmtk

I also filed a bug with NITRC about this, but folks there feel it's not related to their configuration, but a CDash problem.

See

http://www.nitrc.org/tracker/index.php?func=detail&aid=3804&group_id=6&atid=101 [^]
No tags attached.
Issue History
2009-06-08 17:48Torsten RohlfingNew Issue
2009-06-08 17:54Julien JomierStatusnew => assigned
2009-06-08 17:54Julien JomierAssigned To => Julien Jomier
2009-06-08 17:55Julien JomierNote Added: 0016658
2009-06-08 17:58Torsten RohlfingNote Added: 0016659
2009-06-08 18:06Julien JomierNote Added: 0016660
2009-06-08 18:36Torsten RohlfingNote Added: 0016661
2009-06-08 19:49Julien JomierNote Added: 0016662
2009-06-08 22:58Torsten RohlfingNote Added: 0016664
2009-06-08 22:58Torsten RohlfingNote Added: 0016665
2009-06-09 09:02Julien JomierNote Added: 0016668
2009-07-27 14:20Julien JomierStatusassigned => resolved
2009-07-27 14:20Julien JomierFixed in Version => 1.5
2009-07-27 14:20Julien JomierResolutionopen => fixed
2010-02-21 12:33Julien JomierStatusresolved => closed

Notes
(0016658)
Julien Jomier   
2009-06-08 17:55   
Could you try switching the CVS viewer from "ViewVC" to "ViewVC1.1" and see if that does the trick?
(0016659)
Torsten Rohlfing   
2009-06-08 17:58   
With ViewVC 1.1 I get this URL:

http://www.nitrc.org/plugins/scmsvn/viewcvs.php/?root=cmtk//CHANGELOG?r1=34&r2=35 [^]

which is missing the relative path of the file in the repo (trunk/core/).

Actually, this seems to be missing from the ViewVC non-1.1 URL as well, so maybe that's the real problem?
(0016660)
Julien Jomier   
2009-06-08 18:06   
We might have to change CDash to support the URL. It seems that there is a lot of URLs possible for ViewVC. Can this wait until the next release? If not I'll try to send you a patch soon.
(0016661)
Torsten Rohlfing   
2009-06-08 18:36   
No rush here; thanks. I assume you're going to register the availability of the fixed version with this bug, so I should be notified, which is all I'd ask for.
(0016662)
Julien Jomier   
2009-06-08 19:49   
Could you try with selecting "ViewCVS" as the repository browser in CDash? ViewVC is the new version of ViewCVS and looking at the generated URL, it seems that it might work. Let me know.
(0016664)
Torsten Rohlfing   
2009-06-08 22:58   
Ha, okay, this is interesting:

If I use "ViewCVS" AND set the ViewCVS URL to

www.nitrc.org/plugins/scmsvn/viewcvs.php/trunk/core/?root=cmtk

that is, if I include the missing "trunk/core/" part of the URL, THEN it sort of works (I am not getting an NITRC redirect page; looks like they don't allow deep links into the ViewVC).

So I guess the original is a combination of
- having to use ViewCVS even though system is running ViewVC, and
- root of the source tree not being root of the SVN repo, which is strange, 'cos I have had this setup before with no problems...
(0016665)
Torsten Rohlfing   
2009-06-08 22:58   
In previous note, sustitute "NOW getting NITRC redirect page" for "not getting..."
(0016668)
Julien Jomier   
2009-06-09 09:02   
The ViewCVS v.s ViewVC is understandable (ViewVC is the new name for the ViewCVS). The source tree not being root of the SVN repository is another issue and is probably related to CTest somehow. If that works for you I'm going to mark this issue resolved, unless you think there is something else we can do. Thanks again for the report!