Subversion plugin not doing variable substitution for ${path} in "Changeset Format" URL

Ryan Courtnage January 2, 2013

We've installed an configured the subversion plugin. SVN commits are being properly linked to JIRA issues. However, when looking at an issue, on the subversion tab, clicking the revision number will go to a URL like:

https://xxxx.browse.cvsdude.com/cgi-bin/siteplan$%7bpath%7d?revision=14047&pathrev=14047&view=rev

Note the $%7bpath%7d in the URL instead of the path. This results in a 404 from the ViewVC server.

The link to the file diff, however, does translate ${path} properly.

4 answers

0 votes
Peter Callies
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 14, 2013

After working with Atlassian support on this issue, I discovered two relevant items.

  1. They provided substitution patterns that caused ${path} substitution to start working.
  2. Once path substitution was working, I discovered through trial and error that our viewvc configuration didn't like the "root" URL parameter. I removed that parameter and included the root as an explicit portion of the pattern.

Here are the patterns that worked for me:

Changeset Format: http://subversion.xxxx.local:81/viewvc/SS01?revision=${rev}&pathrev=${rev}&view=rev
File Added Format: http://subversion.xxxx.local:81/viewvc/SS01${path}?pathrev=${rev}
File Modified Format: http://subversion.xxxx.local:81/viewvc/SS01${path}?pathrev=${rev}&view=diff&r1=${rev}&r2=${rev-1}&diff_format=h
File Replaced Format: http://subversion.xxxx.local:81/viewvc/SS01${path}/?revision=${rev}&view=markup
File Deleted Format: http://subversion.xxxx.local:81/viewvc/SS01${path}?pathrev=${rev-1}</span<>>

Ryan Courtnage February 18, 2013

But now you aren't using $path in your Changeset Format

0 votes
Ryan Courtnage January 27, 2013

I went back and forth with Atlassian on this for 15 days. They could would not acknowlege that there is a problem. Even though I'd clearly demonstrate that the problem is due to the plugin not doing a pattern/var substituion, I'd get back strange responses like "oh, it's probably an issue with you proxy server" or "it's probably a UTF-8 issue". Very frustrating, I eventually gave up.

If you want to try, feel free to reference case JSP-147757, as it details the problem very clearly.

0 votes
Ryan Courtnage January 27, 2013

I went back and forth with Atlassian on this for 15 days. They could would not acknowlege that there is a problem. Even though I'd clearly demonstrate that the problem is due to the plugin not doing a pattern/var substituion, I'd get back strange responses like "oh, it's probably an issue with you proxy server" or "it's probably a UTF-8 issue". Very frustrating, I eventually gave up.

If you want to try, feel free to reference case JSP-147757, as it details the problem very clearly.

0 votes
Peter Callies
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 27, 2013

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events