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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,412,037
Community Members
 
Community Events
169
Community Groups

Transfer Crucible Reviews from one repository to another

We have to move from Mercurial to Git for all our repositories.

Transfer is not a problem, but we have numerous code reviews in Crucible, which are bound to this Mercurial repositories.

We must not loose the reviews and would like to re-connect the reviews to the migrated Git repos.

It looks like Crucible binds a review to the repository and to the changeset in some way. I am pretty sure, there is no automated way to rebind the reviews, but could anybody tell me, which database table and which column I would have to modify to rebind the reviews to the Git repositories?

1 answer

0 votes

May I ask you why do you want to rebind code reviews?

Can't old reviews be linked with Mercurial repositories, while new ones created against new Git repositories?

Did you consider storing content of file revisions under review? Crucible has such option:

https://confluence.atlassian.com/crucible/storing-all-revisions-under-review-298977548.html

thanks to this, you will be still able to see review content, even if the repository is no longer accessible. 

We will shut down Mercurial soon, after converting the content of the Mercurial repositories to Git. We will not create only new repositories on Git, but continue to work on the existing (to Git converted) repostories and the goal is be able to access the old revievs from the converted Git repository.

Storing content of file revisions under review is not a real solution, because

a) you need a huge additional space to store all the content

b) according to the link, "the storage only applies to reviews created after Revision Storage is enabled"

As far as I saw, the Fisheye/Crucible database stores the changeset hashtag(s) and the repository name for reviews. If I could get a list with Mercurial changeset : Git changeset out of the conversion tool, I should be able to replace the values in the Fisheye/Crucible database, right?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events