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

Not able to code review trunk against another branch Edited

Hallo,

I am testing the free version of FishEye and Crucible 4.4.0 for a svn repo in order to decide if we will acquire the tools, but unfortunately we are not able to make a simple code review display the correct information.

I created the code review by selecting the option "Add content to Review" and then "Choose branches". I wanna compare Trunk against a branch that derives from it. During the creation it shows the correct information:

AddBranch.png

 

But in the codereview the files displayed are from another branch:

WrongBranch.png

And obvisouly the files shown do not correspond to the same as if I just did a normal "svn diff" between the two branches, trunk and new_gui_menu.

What is super strange is that the branch that is displayed in the info panel of the code review, has already been merged into master and it has been already erased(I know in svn all data stays there even if you erase a branch folder). Before the codereview I rebased new_gui_menu on top of trunk in order to have both at the same status.

By the way, the indexing of crucible was already completed and the tool shows that it is updated.

What could be the reason for this missbehaviour? Is there anything else that I still need to configure? Is this a restriction of the free vesion?

1 answer

0 votes

It's not easy to give a good answer without knowing your repository structure, indexing settings and actions you performed in a code review. Few things which comes to my mind:

  • you said you were evaluating the product - maybe you added this second branch via 'Add content > Add changesets' option during your exploration?
  • open repository graph (Repositories > your repo > Commit graph tab) and add these two branches and a trunk and check how they were merged

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...

309 views 18 19
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