search

camunda-community-hub / community-action-maven-release

Opinionated GitHub action to release community projects to Maven Central
Apache License 2.0
7 stars 4 forks source link

Strange errors on releasing (due to legacy-host?) #55

Open stephanpelikan opened 9 months ago

stephanpelikan commented 9 months ago

Releasing my project gives me strange errors:

https://github.com/camunda-community-hub/vanillabp-camunda7-adapter/actions/runs/6247947960/job/16961546227#step:5:1372

OSSRH give the hint to switch from legacy host oss.sonatype.org to new host repo1.maven.org to avoid strange behavior caused by exhausted hosts:

https://issues.sonatype.org/browse/OSSRH-51097?focusedId=1168991&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1168991

More than a year ago I merged my project to Camunda Community Hub and there war already similar strange behavior caused by the legacy host. When do you plan to move to the new host? It is really a bit of annoying that releasing is not reliable. Today I to a talk at a Camunda meetup and wanted to release some fixed upfront, what fails.

berndruecker commented 9 months ago

Hi @stephanpelikan - thanks for reporting.

As the issue suggests these are temporary problems - as it looks the problem finally went away for your specific build - right?

Well, the timeouts might have to do with the fact that you're on our legacy host oss.sonatype.org, which can bog down every now and then. You might consider having us migrate you to the new host, s01.oss.sonatype.org (which is more performant because it hosts fewer projects), but that would require you to have to change your build configuration to use the new hostname.

Switching to the new host is - as far as I know - connected to the group id, so it would require switching org.camunda to s01 completely - which would affect a lot of artifacts also from the product - so this is not within the powers of the community hub. As long as retrying the build occasionally works I think this is still the easiest path forward, even if I understand it is annoying.

As an alternative we could think about changing the group id to io.camunda which as far as I know is on s01. I guess it is your call @xomiamoore how much effort we can put into this.

stephanpelikan commented 9 months ago

Hi @berndruecker, yes it was gone after a couple of hours. I retried it immediately two times but both failed. I created a new ticket because 1.5h years ago, when I hit these kind of errors first, the community-hub team told me to switch and I wanted to know about the status of this plan. Your arguments are reasonable and I can understand why you didn't change so far.

Moving to io.camunda is an option to be considered. @xomiamoore please let me know if and when it will be available for the community-hub-based build.