- Newest
- Most votes
- Most comments
Hello.
If minimizing costs is the only priority, I believe you could set this up for the price of a single EC2 instance by running SonarQube—using Docker, for example—on an EC2 instance configured as a GitHub Actions self-hosted runner.
If they are running on the same EC2 instance, you should be able to access them via localhost.
https://hub.docker.com/_/sonarqube
However, the GitHub documentation below states that there is a risk of permanent compromise by untrusted code executed within the workflow; therefore, from a security perspective, I think it is better to host it on a separate EC2 instance or similar, even though this entails additional costs.
https://docs.github.com/en/actions/reference/security/secure-use?learn=getting_started&learnProduct=actions#hardening-for-self-hosted-runners
Self-hosted runners for GitHub do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
Relevant content
asked 3 years ago
asked 3 years ago
- AWS OFFICIALUpdated 4 months ago
