Child pages
  • Searchable index of repository
Skip to end of metadata
Go to start of metadata

Imported From:

All the work, that is done on In-Portal is being committed in SVN repository. If there is a need to recall some of it later there are 2 ways right now:

  • search issue tracker
  • search google groups

However if there is a need to search through a code-base in every code change that was made in each period of time, then there are no way to do it.

Here is a solution I've came up while surfing the web: It allows to index all content of repository (how much exactly can be specified via settings) and then use Google-alike search queries to find info.

For example if you remember, that some interesting code were having "this" word in it and it was in "test.php" file, then you can easily form a search query to find exactly it.

There is something similar build-in on GitHub.


  1. Hi Alex,

    Interesting topic

    There is a major issue - that SQL Query is in C# / .NET and requires
    Windows servers and so on...

    Not sure if we want / can accommodate it. Any Linux based solutions?


  2. I'm sure there are similar software, that can be run on Linux web server.
    For example FishEye: .

    This is a really amazing product with in-depth code analysis tools,
    including repository search, written in Java. I'm proposing to first look
    at for
    ability to get free open source license for In-Portal.

    We first need to install fisheye on publicly accessible url, like and start using it as Trial for 1 month.
    During that time if Atlassian will confirm our license request then we'll
    get it.

    Dmitry, could you please investigate this (open source license)?

    If no free license possible, then we maybe pay for a license once.

    As another bonus of using FishEye I can add build-in notifications (right
    now we use CVSSpam) along with easy to use repository diffs (right now we
    use ViewVC).

  3. Thanks for clarification Alex.

    Yes, let take a closer look to the project.


  4. We switched to FishEye and issue is no longer relevant.