Open pierre-yves-monnet opened 1 month ago
I can't assign to the correct user or add labels (I don't have the permission I suppose)
Oddly when I reran the Action I got a totally different error:
Error: Cannot read properties of null (reading 'version')
I think this might be the issue, can you update this and see what happens?
I updated to the last version. I try to add some debuging option, without any change. I don't face the "cannot read properties", but still the "bad request".
Error: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (deploy-to-maven-central) on project filestorage: Execution deploy-to-maven-central of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy failed: 400 - Bad Request -> [Help 1]
I re-run using the "debug check box" and I see again the error
Oh, hold on This action should only be used in a release context If you believe this to be an error, please submit a bug report
So, this action is not suppose to be executed on a PUSH, but only when a RELEASE is created! Camunda should change the trigger of this action (and the README to explain we need to create a Release to publish something, which make perfect sense)
So, I create a release, and I got now a new error
Error: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (deploy-to-maven-central) on project filestorage: Execution deploy-to-maven-central of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy failed: Nexus connection problem to URL [https://s01.oss.sonatype.org/ ]: "username" is blank! -> [Help 1]
Same error in debug mode.
Hey @pierre-yves-monnet, I think I might have found part of the issue -- this repository is not registered in our infrastructure setup here --
https://github.com/camunda-community-hub/infrastructure/edit/master/terraform/github/repositories.tf
Was it renamed from zeebe-cherry-filestorage?
Camunda should change the trigger of this action (and the README to explain we need to create a Release to publish something, which make perfect sense)
This is a good point, I am thinking on this to make sure there aren't any unintended effects if I change this 🤔
This issue seems to be related to the other issue: https://github.com/camunda-community-hub/community-action-maven-release/issues/54.
xomiamoore opened a Github issue in the project, asking to upgrade the version. https://github.com/camunda-community-hub/zebee-filestorage/issues/43
I did it, but I faced an error during the publicatoin. I updated the issue, and the error I face is accesible in the action. Here is the result
Error: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (deploy-to-maven-central) on project filestorage: Execution deploy-to-maven-central of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy failed: 400 - Bad Request -> [Help 1]
Could you help me please?