My SCM is SVN and under feature branches of each application there are temporary folders. These folders after a period of time is removed from the feature branches.
Now, if I want configure fisheye to index from a given revision, it begins to index all the logs from SVN server. So it tried to analyze (Importing and Creating Changesets) for removed folders as well. This causes Fisheye to be very very slow.
What I would like to achieve is at a particular revision number, fisheye should index from there on wards only.
But I am not sure how this can be achieved?
Because from development team, they don't want to see old code files for review (in crucible). They would like to review the files which were committed recently.
Let me know your experience.
If I understand correctly, you have set a start revision for your SVN repository but you're still seeing changesets indexed from before that start revision. Is that correct? What did you select for Initial Import?
According to Adding a Subversion Repository:
When a Start Revision is set, this setting controls how FishEye establishes the initial state of the repository.
Do not import means that FishEye will only process the revisions from the start revision onwards. The repository state prior to this revision is ignored.
Import without tag information means that FishEye will import the repository content as it existed one revision prior to the start revision. FishEye will create a single synthetic revision to hold the initial state. The comment associated with this revision will be 'Created by FishEye for initial repository import'. Tags created prior to the start revision are ignored. Due to the synthetic commit the "Last commit" date will display the date "31 Dec 69" in statistics panels.
Am I misunderstanding? It also sounds like you may not want files which exist in a revision, but haven't been changed. If that is the case this isn't currently possible. When you create a review and select a revision to be reviewed, only information that was changed between the selected and the previous revision will be displayed in the review. Please see Creating a review for more information.
If you're having issues with FishEye's performance during the scan, I would recommend reading and trying some of the steps in Improve FishEye scan performance.
One thing that may help is setting excludes. You can configure this by going to Administration >> Defaults >> Include/Exclude Paths tab and click "Add" to add a new include/exclude patterns. To add an Exclude Pattern, place a pattern similar to this except with your desired file type to exclude:
in the 'Add an Exclude' dialogue that will be displayed. For reference here is our documentation on Configuring exclude paths.
Hi Atlassian Community, My name is Avni Barman, and I am a Product Manager on the Confluence Cloud team. Based on feedback from you, we are giving admins more power to create templates that a...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events