> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/disabling-or-changing.md).

# Disabling or changing the mechanisms

In very specific cases, you may have to disable or change the incremental analysis mechanism in SonarQube Server 10.8.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.8 documentation. For a list of all 10.8 pages, see the [SonarQube Server 10.8 page index](https://312504542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiJj3TXBdWssTGGg8qK5I%2Fuploads%2FmeJ1nVNGPezOurNrTy4A%2Fsonarqube-server-10.8-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.8 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

In very particular cases, you may need to disable or change the [Introduction](/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/introduction.md).

## Disabling the Skip unchanged files mechanism <a href="#disable-skip-unchanged" id="disable-skip-unchanged"></a>

You can disable the [Introduction](/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/introduction.md) used by the Kotlin and Java analyzers by setting the `sonar.kotlin.skipUnchanged` or the `sonar.java.skipUnchanged` to `false`.

## Disabling the analysis cache mechanism <a href="#disable-analysis-cache" id="disable-analysis-cache"></a>

In particular cases, you may need to disable the [Introduction](/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/introduction.md).

The analysis cache mechanism is enabled by default. If you disable it, the analyzer will analyze all files from scratch.

To disable the analysis cache mechanism, add the following parameter to your analysis (See [Analysis parameters](/sonarqube-server/10.8/analyzing-source-code/analysis-parameters.md) for information about the setup of analysis parameters for the scanner.):

`sonar.analysisCache.enabled=false`

{% hint style="info" %}
The parameter `sonar.analysisCache.enabled` is not compatible with SonarScanner for .NET.
{% endhint %}

## Using the local filesystem for analysis caching <a href="#configure-filesystem-cache" id="configure-filesystem-cache"></a>

With the C/C++/Objective-C analyzer, you can [Customizing the analysis](/sonarqube-server/10.8/analyzing-source-code/languages/c-family/customizing-the-analysis.md) instead of using the [Introduction](/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/introduction.md) on the server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/disabling-or-changing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.