Gitea SonarQube Bot

A bot that fills Gitea's missing SonarQube integration by decorating Gitea pull requests with SonarQube analysis results, giving developers code-quality…

  • Development
A bot that fills Gitea's missing SonarQube integration by decorating Gitea pull requests with SonarQube analysis results, giving developers code-quality feedback directly in their reviews.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

6/100 Low

Maintained
0last commit 1493 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2022-10-20
License
MIT
Activity
stale

Checked 14 days ago - source: GitHub (siruoren/gitea-sonarqube-bot)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start Gitea before anything else Run `gitea web` to start the Gitea web server, and if you use `--port` or `--config`, make sure that port is reachable and the config file is the one you want. Without a running server, the Gitea web UI and API are unavailable. source
  • Tell pip where Gitea packages live For Python packages, point pip at your Gitea registry with `--index-url` and include your Gitea username and password or token in the URL. Without that index URL, pip looks only at public PyPI and may not find packages stored in Gitea. source
  • Use your own Gitea username The examples use `testuser`, so replace it with your real Gitea username in package URLs. If you leave the wrong owner, installs can target the wrong registry and fail. source

Fetched 41 days ago - each note links to its source

Alternatives (12)

  • Bitbucket - Offers Git-based code hosting, integrated issue tracking, a project wiki, pull requests, and collaboration tools with support for private o…
  • Forgejo - Forgejo is a self-hosted, lightweight Git forge for hosting repositories and managing projects.
  • GitBucket - GitBucket is a self-hosted Git web platform built in Scala that provides a lightweight GitHub-compatible repository, issue, pull request, a…
  • GitHub - Web-based Git hosting service facilitating collaboration, with features like issue tracking, social networking, and wikis for project manag…
  • GitLab - GitLab is a self-hosted Git repository server and software delivery platform for individuals and teams to privately plan, version, build, t…
  • Gitea - Gitea is a lightweight, self-hosted Git service for hosting and managing Git repositories, pull requests, and issues.
  • Gogs - Gogs is a self-hosted Git service for hosting code repositories with web interfaces and Git command-line workflows.
  • Launchpad - Launchpad is a collaboration and Bazaar code hosting platform for (primarily open-source) software projects.
  • Pagure - A Git center project hosting with bug reporting tools.
  • Radicle - Open source, peer-to-peer collaboration on Git enables decentralized, censorship-resistant code sharing, local-first autonomy, and modular…
  • RhodeCode - RhodeCode is a self-hosted code review and repository management platform for Git, Subversion, and Mercurial.
  • SourceForge - Open source community and software directory offering code hosting, analytics, version control, project management, and access to over 50,0…

Checked 40 days ago - source: AlternativeTo

Common questions

How does gitea-sonarqube-bot post SonarQube results to Gitea pull requests?

It uses webhooks to receive analysis results and decorate Gitea pull requests with SonarQube data.

What SonarQube limitation does the bot address?

SonarQube lacks a Gitea ALM integration, and the project says this will not be added in the near future. The bot fills that gap.

Did a user report running the bot on the Gitea server while SonarQube was elsewhere?

A user described installing the bot on the Gitea server with SonarQube Community on a different server and matching project names in the config. They reported that they could not get the integration to work.

Where is the Helm documentation located?

The project repository includes a Helm README in the helm directory.

Answers sourced from codeberg.org, community.sonarsource.com, github.com, github.com

Community

Collected 48 days ago - public community threads