Starter license and very old metadata commit

[Stephane Stephane]

We are in a team of 8 individuals and we're using the starter license to evaluate if fisheye could fit our needs (the company has 150+ developers).

We working on project foo in the incubator (/trunk/incubator/foo). I am trying to add this repository as an example but hit the number of commiters limit because a few people actually changed the metadata of /trunk and /trunk/incubator. What I did was adding http://svn.mycorps.com/myrepo with an include on /trunk/incubator/foo.

How can I circumvent this? I actually don't care about these metadata changes but since it was done by a separate team, it counts and hit the committers limit.

Thanks,

S.

[Sten Pittet]

Hi Stéphane,

If you want to evaluate the product the best option would be for you to use an evaluation license.

You will be able to use FishEye and Crucible with 100 users for 30 days. The simplest path to do this is to

(1) Download the latest version of FishEye here: http://www.atlassian.com/software/fisheye/download

(2) Start your FishEye instance and follow the steps

(3) Choose the evaluation license when prompted

That should be a better way for you to try out the product as you will not have any limitation. You can also include Crucible to your evaluation to leverage code reviews with your team.

Cheers,

Sten

[Stephane Stephane]

Hi there,

Yes I know about the evaluation. I just want to make sure I can still use the tool after 30 days for this small team. Right now, I can't because of a few commits. which are outside the project's space.

Any idea?

[seb]

You would need to set the start revision of the svn repository configuration at a point which those old committers are not visible after.

Documentation can be found here: http://confluence.atlassian.com/display/FISHEYE/Subversion

[Stephane Stephane]

does not work for me. I have added start revision 9365 and I still have commits from that user (#9364)

[Chii]

Did you reindex the repository after setting the start revision? If you have, you should lodge a support case with the debug logs - a user that has only committed prior to the start revision should not show up.