The publish workflow does not work

[julienrf]

I am opening a new issue to follow-up on #18.

Unfortunately, the publish workflow failed with the following error:

Importing private gpg key
Error: The process '/usr/bin/gpg' failed with exit code 2

The cause of this error is likely to be that the credentials are incorrect (see this).

To move forward and make the library widely available to the Java programmers, we need to fix the publish workflow. For this, we need someone with rights to manage the Sonatype authentication credentials to double-check they are correctly set as GitHub secrets, and someone with rights to trigger the workflow to test the result.

Once the workflow works, we will be able to amend it to “automatically release after close” (see here) and publish version 1.0.0.

[guy9]

@yaronkaikov can you have a look?

[Annamikhlin]

I updated the GPG key and it passed this step successfully https://github.com/scylladb/alternator-load-balancing/actions/runs/9937637969/job/27448413720

Importing private gpg key
Received 17021837 of 21216141 (80.2%), 16.2 MBs/sec
Cache Size: ~20 MB (21216141 B)
/usr/bin/tar -xf /home/runner/work/_temp/f879089a-2a15-4363-9ae4-58[30](https://github.com/scylladb/alternator-load-balancing/actions/runs/9937637969/job/27448413720#step:3:32)1b5f24e3/cache.tzst -P -C /home/runner/work/alternator-load-balancing/alternator-load-balancing --use-compress-program unzstd
Received 21216141 of 21216141 (100.0%), 10.1 MBs/sec
Cache restored successfully

currently it failed on Publish step when running the command: mvn -Drevision=0.1.0-RC1 deploy with error:

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  4.079 s
[INFO] Finished at: 2024-07-15T10:17:04Z
[INFO] ------------------------------------------------------------------------
Error:  Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project load-balancing: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error: Process completed with exit code 1.

[Annamikhlin]

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  4.079 s
[INFO] Finished at: 2024-07-15T10:17:04Z
[INFO] ------------------------------------------------------------------------
Error:  Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project load-balancing: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error: Process completed with exit code 1.

according to the error, seems that distributionManagement section is missing in the java/pom.xml

adding this sections in PR: https://github.com/scylladb/alternator-load-balancing/pull/23

[yaronkaikov]

@Annamikhlin Great work !!!!, now it is passing https://github.com/scylladb/alternator-load-balancing/actions/runs/9938994751

@julienrf @guy9 FYI, we can move forward with this

[julienrf]

Thank you all for your help!