Setup SonarQube release and GitHub deployment#47
Merged
Conversation
3dgiordano
approved these changes
Jun 3, 2026
The idea is to be able to layout the release automatically. This way, when release happens, all jars for Jmeter-compatibility will be placed int the release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a complete automation for releasing artifacts to Maven Central, including the necessary Maven configuration, a GitHub Actions workflow, and enhancements to the
pom.xmlfor compliance with central repository requirements. The changes ensure releases are properly signed, documented, and published in a repeatable, secure way.Release Automation and Workflow Integration:
.github/workflows/release.yml) to automate the release process, including version setting, artifact building, signing, deployment to Maven Central, and updating the project version to the next snapshot..github/maven-central-deploy.sh) for securely importing GPG keys and deploying artifacts to Maven Central using Maven..github/settings.xml) to configure authentication and GPG signing using GitHub Actions secrets and environment variables.Maven Project Configuration Improvements:
pom.xmlwith required metadata for Maven Central: added a project description, license, project URL, developer information, and improved SCM connection URLs. [1] [2]releaseprofile topom.xmlthat enforces no snapshot dependencies, attaches sources and javadocs, signs artifacts with GPG, and configures publishing via Sonatype Central.