Starter license and very old metadata commit

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.

2 answers

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

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?

0 vote
Seb Ruiz Atlassian Team Nov 21, 2011

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

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

Joe Xie Atlassian Team Nov 30, 2011

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.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Marketplace Apps

Tips on how to choose the best estimation method for your planning

Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...

71 views 0 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you