Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

The right settings for SVN symbolic rules

Is there a way to make Fisheye and Crucible only show branches/tags for the selected project?

Our SVN repository uses the standard projectName/branches/branchName structure.

When i first added it to Fisheye, I checked "Use built-in symbolic rules", and set the "and then apply..." menu to "None". This was according to the instructions here.

But when I view the changelog for my repository, the "All branches and tags" menu shows branches/tags from all projects, not just the one I'm viewing. And in Crucible, under "add branches to the review", it also shows branches from all projects.

So I tried changing the "and then apply..." menu to the second option (/project/trunk... etc.). With this, the menu lists branches like "projectName-branchName". Is this the desired result? It still shows branches from all projects, not just the selected one.

I'm not sure how this is supposed to work.

1 answer

1 accepted

0 votes
Answer accepted

Hi,

From your description I understand all your projects are under the same SVN repository, is this right?

In this case I think what you want to achieve should be possible if you add each project as a separate repository in FishEye. For instance, let's say you have PROJECT1 and PROJECT2 as follows:

  • /path/to/repository/PROJECT1
  • /path/to/repository/PROJECT2
  • You could add these as separate repositories in FishEye. I think the repository you currently have added has the path /path/to/repository. To add a repository just for PROJECT1 you could add a repository to FishEye named PROJECT1, then restrict the scope for this setting the Repository URL as being /path/to/repository/PROJECT1, or Repository URL as being /path/to/repository and Path as being PROJECT1. The way this will be set depends on what's your Repository Root. A svn info /path/to/repository/PROJECT1 command should help you identifying what should be the Repository Root, which will be put as the Repository URL. The rest goes then as the Path.

Regards,

Gustavo Refosco

Yeah, that's the conclusion I came to as well. It seems like multi-project repositories aren't a good idea in Fisheye for this reason. It might be a good idea to document that.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

467 views 20 24
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