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.
Updated the GitLab CI configuration to properly format the SonarCloud scan script using a multiline approach. This ensures better readability and maintainability of the pipeline configuration.
Switch the base image in the GitLab CI from Bullseye to Alpine. This change reduces image size and improves build efficiency. All pipeline stages remain unaffected.
Switch the base image in the GitLab CI from Bullseye to Alpine. This change reduces image size and improves build efficiency. All pipeline stages remain unaffected.
Switch the CI pipeline base image to `maven:3-amazoncorretto-17-slim-bullseye` for a lighter and more efficient build environment. This change reduces unnecessary overhead while maintaining compatibility.
Switching to the new base image ensures compatibility with the latest repository updates. This change may improve build consistency and align with recommended CI configurations.
Switching to the new base image ensures compatibility with the latest repository updates. This change may improve build consistency and align with recommended CI configurations.
Introduced SonarCloud scan and testing stages to the CI pipeline. Defined variables for SonarCloud and added a new `on_commit` stage for running tests. Updated the `.gitlab-ci.yml` configuration to improve project quality checks and automation.
Reorganized the cloning logic into a dedicated pull stage and updated the cloning script for efficiency. Replaced `rules` with `only` to clarify job triggers and added the `GITLAB_CLONE_DIR` variable for better repository management.
Introduce a `.gitlab-ci.yml` file with a job to clone a GitHub repository using a personal access token. The pipeline is scheduled to run daily via a cron rule, ensuring the repository stays in sync.
Made minor changes to enhance readability and consistency in phrasing within the README file. Adjusted descriptions to make them more concise and user-friendly.
Updated the README to include instructions for integrating the project into a Maven-based setup, like adding the repository and dependency configurations. These changes assist developers in easily utilizing the library.
Reorganized the `scm` block and added a `distributionManagement` section for publishing to GitHub Maven Packages. Cleaned up unused plugin configurations and improved XML formatting for better readability.
Updated the README to correctly format the GitHub release badge and its hyperlink. This enhances clarity and ensures the badge integrates seamlessly with the text.
Reverted the version from 0.1.1-SNAPSHOT to 0.1.0-SNAPSHOT for alignment with the development lifecycle. Ensures consistency with planned versioning strategy.
Moved javadoc configuration and execution into a dedicated profile to improve build configuration modularity. This change ensures the javadoc generation is optional and can be controlled via the `javadoc` profile activation.
This update configures the Maven release plugin to include the `-DskipTests` argument. It ensures tests are skipped during release processes, speeding up build times for releases.
Added badges for quality gate status, security rating, coverage, lines of code, and code smells from SonarCloud. These provide better visibility into the project's code quality and metrics directly from the README.
Renamed the `mvn-test` job to `mvn-sonar` for better clarity and alignment with its purpose. Additionally, corrected a typo in the Sonar project key to ensure accurate project identification.
Consolidated the Maven build and SonarCloud analysis into a single step for efficiency. Removed redundant workflow definitions and ensured proper environment variable handling. This change reduces complexity and streamlines the CI/CD workflow.
Introduce a new job in the GitHub Actions workflow to integrate SonarCloud analysis. This includes setting up JDK 17, caching Maven dependencies, and running the SonarCloud Maven plugin for code quality checks.
Configured SonarCloud properties for code analysis and reporting. Integrated JaCoCo Maven plugin to generate code coverage reports in XML format for SonarCloud. These changes enhance code quality metrics and monitoring.
Included a GitHub release badge to display the latest release version directly in the README. This improves visibility of the project's current state and provides quick access to the release details.
Regenerated all Javadoc files with updated timestamps and fixed an example snippet in `CfDnsClient` for consistent variable naming. This ensures updated documentation and code clarity.
Added an entry for a javadoc script path in .gitignore to exclude it from version control. Also, introduced a custom CSS file to override specific styles in jQuery UI, primarily adjusting active state colors and borders.
Refactored HTTP request methods by removing explicit `responseType` parameters where possible and adjusting to specific response mapping needs. Additionally, updated Javadoc documentation language from German to English for consistency, improving clarity and accessibility.
Replaced the broken relative javadoc link with a working absolute URL pointing to the hosted documentation. This ensures easier access to the API reference for users.
The javadoc.sh script was specific to a local environment and is no longer needed. Removing it ensures cleaner code and avoids confusion or potential misuse.
Introduce Javadoc-related files (`javadoc.sh`, `options`, and `packages`) for API documentation generation. Update README to improve clarity on usage examples and remove redundant "Example" headings for a cleaner presentation.
Expanded the API documentation by including practical examples for the `CfDnsClient` class. Updated Javadoc metadata and modified the index.html title for better context.
thischwa
Thilo Schwarz