The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a SVN structure which is something like this:
/svn/product/component1/service/trunk
/svn/product/component1/service/branches/branch1
/svn/product/component1/client/trunk
/svn/product/component2/service/trunk
/svn/product/component2/client/trunk
...
I have configured the repository to
SVN URL /svn/
Path /product/
I did not want to have all the components in one trunk, so I configured custom SVN Symbolic Rules. For example:
Trunk
Regular Expression ([^/]+)/([^/]+)/trunk(/|$)
Name ${1}-${2}-trunk
Logical Path Prefix ${1}/${2}
Branches
Regular Expression ([^/]+)/([^/]+)/branches/([^/]+)
Name ${1}-${2}-${3}
Logical Path Prefix ${1}/${2}
Testing I get:
/component1/service/trunk/path/to/file.java
Container trunk:component1-service-trunk
Logical Path component1/service/path/to/file.java
Logical Tail path/to/file.java
/component1/service/branches/branch1/path/to/file.java
Container branch:component1-service-branch1
Logical Path component1/service/path/to/file.java
Logical Tail path/to/file.java
To me that looked good so far. However, creating a branched-based review, I run into errors. First error is that there is no "trunk" which is obvious in my configuration. However, if I select the proper "${1}-${2}-trunk", I get the error "Attempt to add too many revisions to a review - no more than 800 file revisions are allowed."
Looking into the Commit Graph, no branching can be seen either.
Point being: is Fisheye unable to handle "dynamic" trunk names like this? Do I absolutely have to use "trunk"?
There is a bug that FishEye and Crucible will always assume there is a a trunk with "trunk" name in any svn repository. This will appear in :
I have created a bug https://jira.atlassian.com/browse/FE-5558 and thats why you are getting the first "there is no trunk" error.
However I am unable to reproduce the problem that the branch review would try to include the initial base branch in the review. Also the fact that the Commit Graph is not showing branching is worrying.
Could you please tell me:
Best regards,
Mac
Hi Steffen,
Thanks for your report.
The problem you're seeing seems similar to the known issue with branch reviews for certain SVN custom symbolic rules configuration. This is tracked as https://jira.atlassian.com/browse/CRUC-7040, please watch that issue for updates.
Your symbolic rules configuration looks okay at a glance, and branch reviews should be able to cope with having multiple trunks. We'll investigate and update further via the JIRA issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.