search

eclipse-pass / main

Catch all repository against which issues of general, cross cutting topics are logged.
Apache License 2.0
4 stars 8 forks source link

Investigate combined java release sonatype error retry #939

Open rpoet-jh opened 9 months ago

rpoet-jh commented 9 months ago

During the 1.4.0 release, the combined java release workflow failed with:

SEVERE: A message body reader for Java class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and Java type class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and MIME media type text/html was not found

There is retry logic in place, but it didn't happen.

Here is the link to the gh action log:

https://github.com/eclipse-pass/main/actions/runs/8081926535/job/22081581722#step:9:9005

markpatton commented 8 months ago

The "retry logic" is for the case that Sonatype reports an error releasing the staging repo, but the artifacts actually make their way to Maven Central. In that case, the action should just proceed on. But in this case we manually checked and the artifacts never made there way to Maven Central. So the action correctly stopped with an error.

Separately we might add actual retry logic for the case of Sonatype reporting an error. If Sonatype reports an error, we could just retry it a few times with something like 5 minute waits.

markpatton commented 8 months ago

Agreed that we should just do a complete sonatype retry when it completely fails. Should update this ticket or open a new one.