This package is designed for use as part of a UDS Software Factory bundle deployed on UDS Core.
SonarQube needs connection to a PostgreSQL instance either in cluster or external. It finds this connection via the sonarqube_db_endpoint
variable declared in the zarf package and configured (as an example) at deploy time by the uds bundle config.
For local testing and CI, SonarQube is bundled with the dev-postgres package.
Flavor | Description | Example Creation |
---|---|---|
upstream |
Uses upstream images within the package | zarf package create . -f upstream |
registry1 |
Uses images from registry1.dso.mil within the package | zarf package create . -f registry1 |
NOTE:
registry1
flavor only supports the amd64 architecture
The released packages can be found in ghcr.
*For local dev, this requires installing uds-cli
Task | Description | Example |
---|---|---|
setup-cluster | Uses the k3d-core-istio bundle to create a cluster for testing against |
uds run setup-cluster |
create-package | Creates just the SonarQube package | uds run create-package --set FLAVOR=<flavor> |
create-test-bundle | Creates SonarQube and SonarQube dependency packages and then bundles them | uds run create-test-bundle |
deploy-package | Deploy SonarQube package only | uds run deploy-package |
deploy-test-bundle | Deploy SonarQube and SonarQube dependency bundle | uds run deploy-test-bundle |
test-package | Run checks against a deployed package or bundle | uds run test-package |
cleanup | Teardown the cluster | uds run cleanup |
Please see the CONTRIBUTING.md