This change addresses long standing issue where the 2nd phase of indexing goes through even though history cache creation/update for one of the repositories failed. If projects are enabled and one of the repositories for given project failed history cache creation/update, that project will not be indexed; the projects with all their repositories being fine w.r.t. history cache are allowed to progress to 2nd phase of indexing. If projects are disabled, history cache creation failure of a repository results in the 2nd phase of indexing being skipped altogether.
Obviously, this relies on the individual repository implementations to properly report the history cache operation failure via HistoryException.
To suppress the new behavior, one can use the --ignoreHistoryCacheFailures indexer option.
This change addresses long standing issue where the 2nd phase of indexing goes through even though history cache creation/update for one of the repositories failed. If projects are enabled and one of the repositories for given project failed history cache creation/update, that project will not be indexed; the projects with all their repositories being fine w.r.t. history cache are allowed to progress to 2nd phase of indexing. If projects are disabled, history cache creation failure of a repository results in the 2nd phase of indexing being skipped altogether.
Obviously, this relies on the individual repository implementations to properly report the history cache operation failure via
HistoryException.To suppress the new behavior, one can use the
--ignoreHistoryCacheFailuresindexer option.