Fisheye: Have to review new branch without any changes

[Peter Trubshaw]

Hey Guys,

We've integrated Fisheye/Crucible with Jira and trying to get code reviews to work without massively changing our working practices.

We're using SVN and our development model dictates that we create a branch in order to do any developement (feature branching model). We methodically label our branches with the Jira ticket name so all changes to the branches do get picked up successfully.

The problem is when we create a branch, it creates a changeset that needs to be reviewed with adding 1400 files. After the initial branch - we can then see the changesets that actually need to be reviewed.

is there anyway that we can (automagically) ignore the actual branch creation from our reviews?

[Martin Cooper]

Fisheye does not ignore Branch creation commits, this is a long standing feature request:

https://jira.atlassian.com/browse/FE-184

What it does if taught your branch structure is make re-use of the same files, as opposed to storing multiple copies. Fisheye does not sit directly on the SVN repository so cannot make use of SVN cheap copies, but uses working copies, which would contain duplicates as a working copy is full file download. By teaching fisheye your structure it can implement its own 'cheap copy' to save space.

[Alexander Taler]

Where does it tell you that the changeset needs to be reviewed?

[Renjith Pillai]

I was under the impression that if the directory structure of the repository follows the ideal case as explained in this link, the branch creations are ignored by Fisheye. Can you go through the link and check whether your repositories requires some special to match the directory structure?

http://confluence.atlassian.com/display/FISHEYE/SVN+Tag+and+Branch+Structure