sfeir-open-source / sonar-clover

It provides the ability to feed SonarQube with code coverage data coming from Atlassian Clover

Apache License 2.0

15 stars 25 forks source link

Problems with release after the bintray shutdown #47

Closed Tony-Proum closed 3 years ago

Tony-Proum commented 3 years ago

We have to release a fix in order to allow groovy support. Also as bintray have been shutdown, we have to re-release the 4.1 with the new Release system.

45 and #46

In order to release a new version we have to migrate our package repository from bintray

Tony-Proum commented 3 years ago

FYI: we have to follow a specific process in order to get access to our new artifact repository, you can find more information here: https://issues.sonatype.org/browse/OSSRH-67181

Tony-Proum commented 3 years ago

🎉 We now have a brand new artifact repository, next release is coming. Sorry for the delay ! TODO:

~~Change some things in pipeline to be able to use this new repository~~
~~Push a sonarcloud analyse during the release~~
~~The validation of the artifact failed due to missing signature~~
Notify Sonarsource that the repository changed, and create a new release in the marketplace

~~EDIT: I have some difficulties with the sonarcloud part for now, I'm almost certain that the problem is PEBKAC but can't figure out what's wrong for now: I have a it works on my machine syndrome.~~ Solved

EDIT 2: I have now an issue when trying to use the gpg private key in github action, this time again, it work on my machine so I'm trying to figure out what's happen. (I suppose that the format of the key is not valid using github secrets)

Tony-Proum commented 3 years ago

The 4.1 were pushed manually on the sonatype repositories. Sonatype have been notified and we now have to wait for the sync with maven central to be activated in order to allow the SonarQube Marketplace to reference the new artifact location

Tony-Proum commented 3 years ago

🎉 The 4.1 is now back to the sonarqube marketplace, for the 4.2 I will have to push the version manually as it remains some issue with github action and the GPG key that I cannot figure out for now. But well in order to not lock this version I will release it manually and follow the process to promote this version in the marketplace soon.

Tony-Proum commented 3 years ago

We seems to have an issue with the 4.2 : https://github.com/sfeir-open-source/sonar-clover/issues/44