Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Configuring SVN Symbolic links

I just can't seem to figure this out.

Our SVN settings looks like this:

Name: modules
URL: https://ourserver/svn/RnD_software
Path: Module

Now the structure is as follows:

 

https://ourserver/svn/RnD_software/Module/HWspecificCode/Common/(trunk/branches/tags)
https://ourserver/svn/RnD_software/Module/HWspecificCode/ProjectA/(trunk/branches/tags)
https://ourserver/svn/RnD_software/Module/HWspecificCode/ProjectB/(trunk/branches/tags)
https://ourserver/svn/RnD_software/Module/HWspecificCode/ProjectC/(trunk/branches/tags)

 

 

For Crucible we have multiple projects but they each point to multiple (sometimes overlapping) SVN projects. For example:

Repository: modules
HWspecificCode/Common
HWspecificCode/ProjectA
HWspecificCode/ProjectB

Would I need anything specific for them SVN Symbolic Links settings and if so, what exactly? In them examples they refer to "project" what does project relate to? FishEye/Crucible project (name) or just the SVN folder?

1 answer

Project in crucible refers to whatever you want it to refer to.  This is the grouping under which reviews occur. It is primarily used to configure things like permissions, who can access, review etc. Though the applications run together under the same server config they really are two separate apps that reference each other.

It sounds to me as though you're over thinking this a bit (Something I am guilty of frequently).  Fisheye and Crucible both point to paths in SVN, nothing more than that.  There isn't any magic going on here.  Symbolic links or physical paths should resolve to the same thing.  Just a location on the filesystem when the repository path (designated by your configuration) is accessed.

I would expect your example: https://ourserver/svn/RnD_software/Module to show the tree for the three Subfolders listed above A B and common.

If you wanted to get more granular in your fisheye and in your crucible configure them down to the A, B, and Common folder above.  (Yes, enter all three under three configurations). That is what I would probably do.

This might make more sense since your branches/tags/trunks folders refer to that level. 

Otherwise I don't think Fisheye will be able to do a good job of displaying branches because you're referencing too close to the root in the tree.  If you're supporting multiple branches of development concurrently this will become important. It will allow you to use the commit graph with your branches.  This is perhaps the most inspired tool in the Fisheye arsenal.

Fisheye will display whatever you configure.  So if you define a repository location of Common you can configure it with a root path of https://ourserver/svn/RnD_software/Module/HWspecificCode/Common then your branches, tags, and trunk folder will behave as expected.  In that case I'd leave the "module" field blank in Fisheye repo config.  (I think this is right, you may need to back off to HWSpecificCode in your repo url and use Common as your module. play with it, no harm no foul if you change it.  Just reindexing which can take a while.) 

Now, if you have occasion to want to see them all in the same view you can configure a fourth repository that accesses all three folders (A, B, Common) together in the same view by configuring it as you have it now.  This could be handy for certain things, but you'll be hitting each folder more than once in the indexing so there will likely be a performance hit.

The reason why it is important to configure with your branches/tags/trunk at the level I describe above is that when you tag, or branch, you are doing so at that level in the repository, not at the https://ourserver/svn/RnD_software/Module/HWspecificCode level which you have described above.

Hope this helps.  (it's not really as complicated as it seems, but I know how confusing this can be when you're first getting started).

 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

Share your Confluence Cloud experience for a chance to win $500!

Take our 5-minute survey to win a $500 Visa gift card! Are you currently using Confluence Cloud? We want to hear from you! Fill out this quick survey about your Confluence Cloud experience so we ...

205 views 4 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you