Skip to content

Revisit Sonar for Terasology #5244

@jdrueckert

Description

@jdrueckert

Motivation

We do have sonar tasks in our gradle setup, but as @BenjaminAmos mentioned in a comment on #5194, we neither have any documentation on how to run SonarQube scanner on Terasology engine, nor does it seem to be run in CI.

Proposal

We should decide whether or not we want to keep sonar based on the benefits it brings.
If we decide to keep it, we should properly set up the scanner in CI and document how to run it manually.
For the latter case, we can have a look at our website repo where it is integrated as a GitHub app.

Alternatives

If we decide to not keep it, we should remove the related gradle tasks and dependencies from this repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Category: Build/CIRequests, Issues and Changes targeting gradle, groovy, Jenkins, etc.Category: Test/QARequests, Issues and Changes targeting tests and quality assuranceRevive: Keepissue has been looked at and deemed potentially helpful for reviveStatus: Needs DiscussionRequires help discussing a reported issue or provided PRTopic: StabilizationRequests, Issues and Changes related to improving stablity and reducing flakynessType: RefactoringRequest for or implementation of pure and automatic refactorings, e.g. renaming, to improve clarity

    Type

    No type

    Projects

    Status

    No status

    Status

    No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions