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.
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.
Adjusted code style to align with consistent brace formatting and removed the null/blank check for `baseUrl` in the constructor. Added unit tests to verify exception handling in `CfDnsClient` for null arguments.
Updated the constructor in CfBasicHttpClient to include explicit throws for IllegalArgumentException. This enhances clarity and ensures the method signature reflects the potential for exceptions. Minor formatting adjustments were also made for improved code readability.
Replaced the Javadoc link in the README with the updated URL and deleted the obsolete `docs/README.MD` file. This ensures that the documentation points to the correct and current resources.
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.
Corrected the version format to match standard semantic versioning. This ensures consistency and avoids potential confusion for users copying the dependency snippet.
Corrected the version format to match standard semantic versioning. This ensures consistency and avoids potential confusion for users copying the dependency snippet.
Replaced the Maven repository URL with the new GitLab package URL and updated the dependency version from `0.1.0-beta.1` to `0.1.0.beta-2`. This ensures compatibility with the latest hosting and artifact version.
This workflow is no longer needed as the repository cloning task has been deprecated or moved. Removing it helps streamline the GitHub Actions setup and eliminates unnecessary maintenance overhead.
Removed the build-and-test.yml GitHub Actions workflow, including Maven build and Sonar integration. Introduced a new workflow to clone a GitLab repository daily using a scheduled cron job.
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.
Refined the `sonar.exclusions` configuration in `pom.xml` to account for all subdirectories under `docs`. This ensures proper exclusion of nested files during SonarCloud analysis.
Changed the Sonar exclusions path from `src/docs/**/*` to `docs/**` for better alignment with the project's folder structure. This ensures accurate exclusion of intended files during analysis.
Updated the project identifiers and added tokens to SonarCloud badge links in the README for improved integration. These changes ensure accurate data retrieval and display on the project status badges.
Excluded `src/docs/**/*` from SonarCloud analysis to avoid unnecessary scans of documentation files. This helps focus the analysis on relevant source code and improves overall build clarity.
admin
thischwa