Atlassian Fish Eye Crack
Welcome to Atlassian Crucible with FishEye. To report a bug or suggest a feature please raise an issue in our public JIRA. Customize this welcome note. Whether you're coding, debugging, testing, refactoring, or just keeping an eye on the codebase, FishEye puts the info you need where you want it: JIRA issues, Bamboo builds, email/ RSS alerts, OpenSocial Dashboards or your IDE! Atlassian.Crucible.and.FishEye.v2.3.3.Incl.Keygen.and.Patch-iNViSiBLE Information: Crucible gives your team an efficient way to benefit from the power of constant code review. Inline commenting, simple workflow, asynchronous reviews, JIRA integration and much more. With Crucible handling the 'administrivia', your.
Fish Eye Meaning
Fish Eye Wart
I want to determine lines of code (LOC) in a subversion repository. Specifically, I want to determine how many lines of code my team supports in production (which is synonymous with our trunk). I've heard mostly good things about Atlassian's FishEye tool so I downloaded a version and started crawling the repository to capture data. As you can see here, the LOC metric is not available and there is an error message which states, 'This plugin does not have access to all the repository data for ESM/. Some data is not available: The repository may be indexing, may not support LOC or has 'Store Diff Info' turned off.'
I've confirmed the Store Diff Info option is selected for the repository based on the information provided here. Is there a way to determine if our repository supports LOC or what might specifically be the problem?
Thank in advance,Brandon
Jordan Dea-MattsonFish Eye Pictures
1 Answer
Fisheye supports LoC for Subversion repositories in general, but it collects that data only for trunk; check that commits to trunk are actually being recognized as such -- since Subversion does not require you to use /trunk as trunk, Fisheye's default symbolic rules may not work.