-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAT-16091 DevOps :: Configure liquibase-hanadb repo to use build-logic #163
Conversation
Label error: This PR is being prevented from merging because you have not added one of the labels: breakingChanges, newContributors, notableChanges, sdou, skipReleaseNotes, TypeBug, TypeEnhancement, TypeTest. You'll need to add it before this PR can be merged. |
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
…file and configure report format feat(pom.xml): add system property variable for spock-reports output directory feat(pom.xml): add dependency for surefire-junit47 to force using the latest JUnit 47 provider
…bility management
…elopment purposes chore(pom.xml): update project name to "Liquibase Extension: SAP HANA support" for clarity chore(pom.xml): update project description to reflect the purpose of the extension chore(pom.xml): update organization name to "Liquibase" for consistency chore(pom.xml): update license information to use Apache License, Version 2.0 chore(pom.xml): update issue management URL to point to the GitHub repository issues chore(pom.xml): update SCM information to use Git and point to the GitHub repository chore(pom.xml): update liquibase.version property to 0-SNAPSHOT for development purposes chore(pom.xml): update project.build.sourceEncoding and project.reporting.outputEncoding to UTF-8 chore(pom.xml): update surefire-plugin version to 3.1.2 for compatibility chore(pom.xml): update build-helper-maven-plugin version to 3.4.0 for compatibility chore(pom.xml): update maven-javadoc-plugin version to 3.5.0 for compatibility chore(pom.xml): update maven-source-plugin version to 3.3.0 for compatibility chore(pom.xml): update jacoco-maven-plugin version to 0.8.11 for compatibility chore(pom.xml): update sonar-maven-plugin version to 3.9.1.2184 for compatibility chore(pom.xml): update liquibase-sdk-maven-plugin version to 0.10.20 for compatibility
chore(pom.xml): update liquibase.version property to 4.24.0 chore(pom.xml): remove unused dependencies and plugins chore(pom.xml): update maven-surefire-plugin version to ${maven-surefire-plugin.version} chore(pom.xml): update maven-failsafe-plugin version to ${maven-failsafe-plugin.version}
… dependencies are downloaded and project is built before running tests chore(test.yml): create HXE directory before starting Hana to ensure it exists
The liquibase/build-logic workflows have been updated to version v0.5.3. This update includes the following changes: - attach-artifact-release.yml: Updated to v0.5.3 - build-nightly.yml: Updated to v0.5.3 - codeql.yml: Updated to v0.5.3 - create-release.yml: Updated to v0.5.3 - release-published.yml: Updated to v0.5.3 - test.yml: Updated to v0.5.3 These updates are necessary to ensure that the workflows are using the latest version of the build logic and take advantage of any bug fixes or improvements that have been made.
…iquibase repositories feat(test.yml): add Liquibase repositories and servers configuration to enable access to Liquibase dependencies The changes in this commit add the necessary configuration to the test workflow to look for dependencies in the Liquibase repositories. This is achieved by adding a maven-settings-xml-action step that configures the repositories and servers for Liquibase. The repositories are configured with the URLs for the Liquibase and Liquibase Pro repositories, enabling access to their releases and snapshots. The servers are configured with the necessary credentials to authenticate with the Liquibase and Liquibase Pro repositories. This allows the workflow to install the liquibase-core 0-SNAPSHOT dependency.
…ema changes The liquibase-sdk-maven-plugin is added to the project's pom.xml file. This plugin will be used to manage database schema changes using Liquibase.
…nclude githubToken environment variable The configuration for the liquibase-sdk-maven-plugin has been updated to include the githubToken environment variable. This allows the plugin to access the token for authentication when interacting with GitHub.
fix(pom.xml): remove unused liquibase-sdk-maven-plugin from pom.xml to reduce unnecessary dependencies
The .DS_Store file was deleted as it is an unnecessary file that is automatically generated by macOS. It is not needed for the project and can be safely removed.
…tegration with GitHub Actions feat(pom.xml): configure the plugin to use the GITHUB_TOKEN environment variable for authentication with GitHub API
Kudos, SonarCloud Quality Gate passed! |
chore(test.yml): comment out the upload-artifact step for test-reports-integration to prevent unnecessary artifact uploads
chore(pom.xml): add SCM information for liquibase-hanadb repository
Kudos, SonarCloud Quality Gate passed! |
https://datical.atlassian.net/browse/DAT-16091