Fisheye/Crucible - incremental indexing after pulling each commit from Mercurial repository.

Tatiana Shambereva

Fisheye/Crucible - incremental indexing after pulling each commit from Mercurial repository.
It lasts for two hours.

Why do we need this?
How can I disable reindexing?
Why don't we index only the files from the commit?

 

Fisheye/Crucible Version:4.4.1

Grzegorz Lewandowski

Incremental indexing and full reindex are two different things:

* incremental indexing is the thing you'd like to have -> pull newest changes and index new commits only

* reindex means dropping current repository indexes and indexing repository from scratch

 

In order to see updates on a repository in Fisheye you need incremental index. In order to determine why it takes 2h first of all determine if Fisheye commences incremental indexing or full reindex. You'll be able to find it in debug logs.

If it's really reindex then I suppose somebody is triggering that in some way (plugin, rest webhook etc) 

If it's incremental index then I suggest enabling debug logs and determining which part takes 2h. Is it connectivity issue and Fisheye is having hard time to pull changes up ? Is this a big changeset with massive changes therefore indexing takes its time ? Hard to tell at the moment.

The third option that comes to my mind is the fact that potentially you have repository polling set to every 2 hours in Fisheye. This means Fisheye will look for new changes in repository every 2h, effectively it seems like a lot of time for Fisheye to pick up changes but in fact it's not, it's jus the polling period.