You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automate publishing of DefectDojo Java Client release to maven central #35
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.
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?
changed the title [-]Automate Relase of DefectDojo Java Client[/-][+]Automate publishing of DefectDojo Java Client release to maven central[/+]on May 24, 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.
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.
Activity
J12934 commentedon May 23, 2023
Mhh? It's automated: https://github.com/secureCodeBox/defectdojo-client-java/blob/main/.github/workflows/publish.yml
Getting automatically published when a github release is created. @Weltraumschaf
Weltraumschaf commentedon May 23, 2023
Build is automated, but there is no such release in Maven Central.
J12934 commentedon May 23, 2023
@Weltraumschaf should publish to maven central when the release doesn't contain snapshot
https://github.com/secureCodeBox/defectdojo-client-java/blob/main/build.gradle#L81
Weltraumschaf commentedon 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 commentedon 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 commentedon May 23, 2023
We also need to meet some requirements:
Documentation how to do this with Gradle.
[-]Automate Relase of DefectDojo Java Client[/-][+]Automate publishing of DefectDojo Java Client release to maven central[/+]Weltraumschaf commentedon Jun 5, 2023
I've raised an comment in the OSSRH issue and asked how to add more maintainers.
Weltraumschaf commentedon Jun 7, 2023
@J12934 and me now have publish rights to our Sonatype staging repo. Now we can test a first release.
Weltraumschaf commentedon Jun 28, 2023
Gradle documentaton from sonatype
secureCodeBox#35 Add basic formatting config
45 remaining items
#35 Migrate from Gradle to Maven
#35 Add build information
Weltraumschaf commentedon 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.
#35 Please use a globale ignore file for common ignores
#35 Migrate from Gradle to Maven
#35 Add build information
Zero3141 commentedon 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
mainbranch. However, this setting mentions thatRequired 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 commentedon Aug 10, 2023
We have weakened the branch protection rules to decouple the release process from Issue 157.
Weltraumschaf commentedon Aug 10, 2023
@Zero3141 Can we add to the action that it updates the version in the README.md?
defectdojo-client-java/README.md
Line 21 in 9a5811c
defectdojo-client-java/README.md
Line 28 in 9a5811c