Updated the SonarQube project key in `pom.xml` to reflect the new naming convention. Simplified the CI script by removing redundant project key specification, ensuring consistency and maintainability.
Removed the hardcoded version of the Sonar Maven plugin to use the latest available version. This ensures compatibility with updates and reduces maintenance overhead.
Added `sonar.sourceEncoding` and updated Sonar Maven plugin to a specific version for improved compatibility. Adjusted SCM values to reflect the correct repository URLs under the `thischwa` namespace.
Replaced Sonar Scanner CLI with Maven Sonar plugin in the CI workflow for better integration and simplicity. Added SonarCloud configuration properties to `pom.xml` for centralized management. This streamlines the setup and ensures consistency across the project.
Replaced outdated project directory, project key, and organization values with updated ones. This ensures proper integration with SonarQube and maintains accuracy in the pipeline configuration.
Removed the `sonar.sources` property as it is redundant in the current setup. SonarQube automatically detects source files, simplifying the configuration. This ensures the pipeline remains clean and easier to maintain.
Added the `-Dsonar.sources` property to specify the `src/main/java` directory for SonarQube analysis. This ensures the main Java source files are included in the scan, improving code quality assessment accuracy.
The test exclusions were overly broad and unnecessary as the tests are handled properly without them. This change simplifies the configuration while maintaining the intended functionality.
Added the `sonar.tests` property to specify the test directory for SonarQube analysis. This ensures better accuracy in test coverage measurement and aligns with the project's structure.
The GitLab CI configuration variables have been updated to reflect changes in the project location. The updates include adjustments to the clone directory, project key, and organization, ensuring that Sonar analysis and GitLab CI operations are correctly configured for the relocated project.
Added the Sonar branch name parameter to ensure proper tracking of the 'develop' branch during analysis. This change enhances consistency and accuracy in SonarQube reporting for this branch.
This update introduces a new job to deploy GitLab Pages. The job copies content from the `docs/` directory to the `public/` directory and is triggered only on the `develop` branch.
Cleaned up commented-out SonarQube configuration from `pom.xml` and removed redundant cache settings in `.gitlab-ci.yml`. This simplifies the build configuration and eliminates unused or unnecessary definitions.
Switched issue tracking from GitHub to GitLab in `pom.xml`. Commented out SonarQube configurations in `pom.xml` and adjusted exclusions in `.gitlab-ci.yml` script. These changes align with the project's migration to GitLab and streamlined quality analysis setup.
This change introduces a new 'build' stage to the CI pipeline. It sets up the pipeline for improved clarity and better stage separation, paving the way for future enhancements or steps.
The pull stage is commented out to streamline the CI pipeline. Refactored the build job to generate artifacts while ensuring test tasks depend on the output of the build job. Added dependencies to relevant stages for smoother execution flow.
Added a Maven build step (`mvn clean package -DskipTests`) to ensure compiled binaries are available for the SonarQube analysis. Also specified the `sonar.java.binaries` parameter to point to the correct output directory.
Introduced a consistent cache path for Maven builds by replacing .sonar/cache with .maven-cache. This change optimizes build performance by ensuring proper caching of Maven dependencies across different jobs.
Added project key, organization, and token parameters to the `sonar-scanner` command for better integration and customization. This ensures proper identification and authentication with SonarQube during code analysis.
thischwa