8.2.9. FAQ

Q: How do I make CI fail when new issues are found?

A: Configure the /Results/Dashboard/limit_violations setting in your axivion_config:

  • Set failure_exit_code to specify the desired exit code

  • Set failure_message for diagnostic output

  • Define limits for each issue category to trigger a failure when new violations are detected

For more advanced scenarios, such as counting new violations between analyses, use the dashboard’s HTTP JSON API /api/projects/{projectName}/issues to query issue deltas between the latest and previous analyses, then apply custom post-processing scripts.

Q: Why are Git clones consuming disk space in my database directory?

A: The sourceserver_gitdir configuration creates one Git clone per Axivion project, which is inefficient.

Solution: In version 7.8+, remove the sourceserver_gitdir setting. Axivion will automatically detect the repository and create a single shared clone instead of one per project:

  1. Remove sourceserver_gitdir from the Git configuration

  2. The next analysis will create a shared clone in the new location

  3. Once all projects have been updated, you can remove the old project-specific clones

Dashboard: When using database_mode=managed_upload (formerly upload=true), old databases are automatically cleaned up if automatic project cleanup is enabled on the Projects > Cleanup page of the Dashboard Server settings; see branch project deletion. This cleanup only works if the Git branch is recorded for the project; in CI environments, this requires setting the branch explicitly (see Git Branch and Commit Hash).

Q: How do I switch from GitHub to a different Git provider (e.g., GitLab)?

A: Axivion does not distinguish between different Git repository providers. During analysis, Axivion runs git remote -v to identify the repository URL (including any tokens). This information is stored in the database. To allow the dashboard to access the repository, the user running the dashboard must have the appropriate credentials, such as SSH keys.

Note: Interactive username/password prompts are not supported; credentials contained in the recorded repository URL are used. If you are using database_mode=managed_upload, manual management of repository clones is generally unnecessary.