camunda-platform-7-mail
camunda-platform-7-mail copied to clipboard
camunda-community-hub
Release 1.4.0
Hi devrel team,
could you please publish the version 1.4.0 of this extenion to maven central?
Thank you, Jonathan, Stephan and Ingo
After checking the output of the github action https://github.com/camunda-community-hub/camunda-platform-7-mail/runs/7875671760?check_suite_focus=true I could not find an upload to the nexus staging area.
Maybe the configuration of the github action didn't match the expected release settings?
The release is available under https://artifacts.camunda.com/ui/native/camunda-bpm-community-extensions/org/camunda/bpm/extension/camunda-bpm-mail-extension-run/ in the public Camunda artifactory.
This project was renamed in #49 but not in the infrastructure repo. I've just updated the file with the new name. Can you create release 1.4.1 and try again?
@ingorichtsmeier sorry for not tagging you yesterday. Are you able to create a new release to see if this fixes the issue? This was successful with another project yesterday, so I'm hoping this will fix your issue as well 🤞
Hi @akeller, I will try it next week and keep you updated.
Thank you for your investigation and clarification!
Hi @akeller,
I just tried to publish a new release 1.4.1, but unfortunately I could not find the upload to maven staging area in the output of the github actions.
I found the lines in this output:
2715: Deploy release to Camunda Repository using community-action-maven-release profile
3103: Deply release to Maven Central using profiles community-action-maven-release, oss-maven-central
But regarding to the details, both times the artifacts were uploaded to the camunda artifactory.
I will wait for Jonathans pull request and try again afterwards.
After applying Jonathans pull request I get the same result: Uploading twice to camunda-artifactory, but not to nexus-staging.
We have to dig deeper...
@ingorichtsmeier If I remember correctly, you must not override distribution settings in your pom (like you do here: https://github.com/camunda-community-hub/camunda-platform-7-mail/blob/master/pom.xml#L48) - you must rely on what the parent pom provides, then it should work. Can you try?
Hi @berndruecker and @jonathanlukas, the url for the distibution management was different to the one in the parent.
Now I found the upload to maven staging:
2022-09-05T13:51:47.6683089Z [INFO] Uploading to central: https://oss.sonatype.org//service/local/staging/deploy/maven2/org/camunda/bpm/extension/camunda-bpm-mail-extension-run/1.4.3/camunda-bpm-mail-extension-run-1.4.3.jar
2022-09-05T13:51:57.4657614Z [INFO] Uploaded to central: https://oss.sonatype.org//service/local/staging/deploy/maven2/org/camunda/bpm/extension/camunda-bpm-mail-extension-run/1.4.3/camunda-bpm-mail-extension-run-1.4.3.jar (653 kB at 67 kB/s)
Could you please press the button to release it?
Thank you, Ingo