GeezerVison is showing github.com — Automate publishing of DefectDojo Java Client release to maven central · Issue #35 · secureCodeBox/defectdojo-client-java
Automate publishing of DefectDojo Java Client release to maven central #35ActivityJ12934 commented on May 23, 2023 Weltraumschaf commented on May 23, 2023 Build is automated, but there is no such release in Maven Central. J12934 commented on May 23, 2023 Weltraumschaf commented on May 23, 2023 Long time ago (~4 years) @rseedorff requested access to Maven Central. They said we should release some SNAPSHOT versions before they grant us access to the public repo. Now we should hook up this process. Weltraumschaf commented on May 23, 2023 Found the Sonatype OSSRH issue:
Looks like everything is prepared to perform a release. @rseedorff do you have the GPG key to sign the jars? Do you have your Jira Account working and can login here? Weltraumschaf commented on May 23, 2023 We also need to meet some requirements:
- Supply Javadoc and Sources
- Provide Files Checksums
- Sign Files with GPG/PGP
- Sufficient Metadata
Documentation how to do this with Gradle. changed the title [-]Automate Relase of DefectDojo Java Client[/-] [+]Automate publishing of DefectDojo Java Client release to maven central[/+] on May 24, 2023Weltraumschaf commented on Jun 5, 2023 I've raised an comment in the OSSRH issue and asked how to add more maintainers. Weltraumschaf commented on Jun 7, 2023 Weltraumschaf commented on Jun 28, 2023 added 2 commits that reference this issue on Aug 2, 2023#35 Migrate from Gradle to Maven #35 Add build information Weltraumschaf commented on Aug 3, 2023 We decided to change from Gradle to Maven bc full automatic release is not feasible int the we want it. We tried now for merely a week to get it work. With Maven it seems way more easier. added 3 commits that reference this issue on Aug 7, 2023#35 Please use a globale ignore file for common ignores #35 Migrate from Gradle to Maven #35 Add build information Zero3141 commented on Aug 7, 2023 Problem: We enforce two status checks (DCO & Java Tests) to pass before merging. We already allowed the SCB Bot (who performs the push commit in which the version is bumped in the pom.xml) to push on the main branch. However, this setting mentions that Required status checks will still prevent these people, teams, and apps from merging if the checks fail..
It seems like that this issue is a general issue, see this discussion. Zero3141 commented on Aug 10, 2023 We have weakened the branch protection rules to decouple the release process from Issue 157. Weltraumschaf commented on Aug 10, 2023 @Zero3141 Can we add to the action that it updates the version in the README.md?
|
<version>1.0.0.-beta2</version> |
|
implementation group: 'io.securecodebox', name: 'defectdojo-client', version: '1.0.0.-beta2' |
MetadataMetadataStatusShow more project fields
DevelopmentNo branches or pull requestsIssue actions
|