Differences not shown when 'Start revision' used for repository creation from SVN.
Asked by Krzysztof Labus:

Dear Sir/Madam

I am writing to enquire about creating the review of a branch and a trunk which has been merged.

Our company is considering to buy Crucible license, and at the moment we are testing your tool using evaluation license.

The code is stored in SVN which has about 10 branches. There are over 40 000 commitments stored in the repository.

Every branch contains around 60 000 files in 2 500 directories and subdirectories (over 1.5 GB of code).

We would like to do review before the branch would be merged into the trunk. Please see attached figure1.png file which present described above situation. Is it possible to do it before merging would be done (I mean something similar to pre-commit functionality) ?

We have found a workaround which solves this lacking feature in the following way:

1. Creating a pre-trunk branch which is a copy of the trunk.

2. Merging the development branch to the pre-trunk branch.

After those two steps we created a review. Review was made from repository's view which was added to Crucible at the beginning (view_1). That repository view (view_1) was made on whole repository and it started from its some revision. Review was made on one revision from pre-trunk branch. Revision contained only action described above in point 2. On this review we noticed a following issue: Files which have not been edited in trunk (pre-trunk branch) since revision from which we started scanning a repository and merged with files from development branch was showed as newly created files.

Review is properly created in situation in which we use repository view (view_2) added to Crucible which contains only our pre-trunk branch (base URL + path to branch + some revision). Please see attached figure2.png file which present described above situation. From few reasons this situation is for us not comfortable and not to accept. Is this a known issue ? Will it be fixed ? How we can make a proper review in this situation ? It seems that solution of this problem is scanning all content of repository, but we would like to avoid it. We would like to avoid making a special branch (pre-trunk branch) or special repository view only for this too. Is this another solution of this problem ?

I would appreciate a quick reply.

Yours faithfully,

Krzysztof Labus


Answers:
author: Foong
body: Hi Krzysztof,

> Files which have not been edited in trunk (pre-trunk branch) since revision from which we started scanning a repository and merged with files from development branch was showed as newly created files.

This is normal in SVN as the files in trunk will be copied and added as a new files in the branch. For more information, please refer to <http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html#svn.branchmerge.using.create>
> How we can make a proper review in this situation ? It seems that solution of this problem is scanning all content of repository, but we would like to avoid it. We would like to avoid making a special branch (pre-trunk branch) or special repository view only for this too. Is this another solution of this problem ?

There is no need to make a pre-trunk branch. Please create the review with a patch as stated in this [documentation](https://confluence.atlassian.com/display/CRUCIBLE/Creating+a+Patch+Review).

Regards,

Foong

Atlassian Support Team


Tags: diff

merge