quarkus-verification

Automate the Quarkus verification lifecycle by running a single pipeline that executes build, static analysis, test coverage, and security scanning. This ensures consistent quality gates before merging branches or preparing releases without manual intervention.

GraalVM native image validation ensures your Quarkus application successfully compiles into a native executable and maintains performance health. It verifies compatibility with native compilation requirements as part of the automated verification pipeline.

The Quarkus verification pipeline supports both Maven and Gradle projects. It integrates with your existing build system to execute test coverage analysis via JaCoCo and security scanning without requiring build tool migrations.

Enforce test coverage and vulnerability checks by integrating the Quarkus verification pipeline into your CI/CD workflow. It uses JaCoCo for coverage metrics and OWASP dependency-check plus Trivy to scan for security vulnerabilities before deployment.

You can use Trivy and OWASP dependency-check for Quarkus security scanning. The verification pipeline combines both tools to detect vulnerabilities in dependencies and container images as part of the automated deployment readiness checks.

Native image compilation in Quarkus verification workflows requires GraalVM compatibility, which may limit certain dynamic Java features. The pipeline validates this compatibility but cannot resolve unsupported reflection or runtime proxy generation issues automatically.