-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ecoCode plugin to SonarQube Marketplace #63
Comments
Hello @jycr, it's a very good idea. (plop @glalloue, @jules-delecour-dav, @julien-hertout-neomades , @olegoaer , @mdubois81, @utarwyn ) |
Out of curiosity, who was that? Because I don't remember saying that and I'm the one who typically vets new plugins |
PR on SonarSource update-center-properties has been created: SonarSource/sonar-update-center-properties#389 |
@dedece35 : Do you have the administration privileges of the ecoCode project on Sonarcloud? |
@jycr Another point : there are also two other plugins for mobile part int repository https://github.com/green-code-initiative/ecoCode-mobile (one for andoird, one for IOS). |
I will create another PR for mobile plugins because the "non-mobile" plugins project has a Security Hotspot to fix (see: #69) for SonarCloud Marketplace validation: |
@dedece35 : where can I find/download:
? |
Hi @jycr, there will be the first 1.0.0 release for 2 mobile plugins (android and ios) soon ( there is no 0.2.0 because is the current version in development. |
@dedece35 : thanks for this information. Is ecocode-android-0.1.0.jar compatible with latest version of SonarQube (from 8.9.+ to 9.9 included) ? |
@jycr yes as mentionned here : https://github.com/green-code-initiative/ecocode-mobile |
As mentioned here : https://github.com/green-code-initiative/ecocode-mobile , v0.1.0 not compatible from 8.9 to 9.3 |
PR on SonarCloud marketplace for ecoCode-android 0.1.0 (for SonarQube 9.4+): SonarSource/sonar-update-center-properties#390 |
To clarify, we wanted to impletement index on the Sonarqube Dashboard in order to add "Green bugs" next to "Bugs and vulnerability. What we understood was our plugin needed to be embedded in the "core" code of Sonarqube to access to this dashboard. Last year we met Sonarsource team and they recommended us to prouve that "Green rules" were relevant with tests and measurements (we started this work few month ago and you can see on some rules oh PHP, the result). Not sure that was directly linked to Sonarqube Marketplace. It could be very interesting to integrate the plugin to your Marketplace if it checks all your requierements |
Thanks for that detail. It makes more sense now. |
PR for mobile plugins has been merge with SonarSource/sonar-update-center-properties#389 @dedece35 : do you know when iOS plugin will be released? |
…arSource Marketplace rules From [Deploying to the Marketplace - Requirements](https://community.sonarsource.com/t/deploying-to-the-marketplace/35236): 3. The key of your plugin must be: 1. short and unique 2. lowercase (no camelcase) 3. composed only of [a-z0-9] 4. related to the name of your plugin 5. not just the name of a language (e.g. cannot be java, rust, js/javascript, …) examples of good keys: motionchart, communityphp, scmactivity
@jycr |
green-code-initiative/creedengo-rules-specifications#63 - Fix pluginKey definition to conform to SonarSource Marketplace rules
#63 - Fix pluginKey definition to conform to SonarSource Marketplace rules
@dedece35 : As soon as a release for a plugin will be available with the correct pluginKey, I will submit again a request to SonarSource Marketplace for the corresponding plugin(s). Also, SonarSource needs to be able to test the plugin on their side. Is there a procedure that I could send them so that they can test all the features offered? |
I assume this is just rules? So I just need a project appropriate for each language (or one to rule them all?) so I can take a look at some representative issues. To be clear, I don't need to see every rule in action. I just need to get an idea of how it works / looks |
Hello. For ecoCode Mobile, the complete list of rules to implement in the plugin is here: https://github.com/cnumr/best-practices-mobile |
I'll see the rules once I load up the plugins in a test instance. I need to run the rules against some sample projects. |
For sake of simplicity, you can access our public/demo running instance here : https://sonarqube.ecocode.io/ Click on More Options. Then :
Browse the Android project name webinar_demo |
I need to run this myself. Can you point me to those projects to I can clone & analyze them? Also, I'll need to run analysis for each plugin. |
You can analyse these two Android apps: |
@jycr, regarding "conflicts" on rule keys ... no problem, after checking and reflexion I undertsand : the same key for the same rule in different languages. |
@glalloue: Those modifications were made to meet @ganncamp's request:
|
It's exactly that! :)
|
thanks @jycr all clear ! |
Hi @jycr, you can play with it :p |
…arSource/sonar-update-center-properties Since "core" analyzers have been integrated more tightly with SonarQube, they no longer appear on the Marketplace. So now plugins should no longer explicitly "require" their respective language "core" analyzers. More information: https://community.sonarsource.com/t/new-plugin-ecocode-requesting-inclusion-in-sonarqube-marketplace/85398/20
…arSource/sonar-update-center-properties Since "core" analyzers have been integrated more tightly with SonarQube, they no longer appear on the Marketplace. So now plugins should no longer explicitly "require" their respective language "core" analyzers. More information: https://community.sonarsource.com/t/new-plugin-ecocode-requesting-inclusion-in-sonarqube-marketplace/85398/20
The ecoCode plugins for Java, PHP and Python have been published on the SonarSource Marketplace. I suggest closing this ticket. For other plugins, I think it's best to create a specific ticket for each one. |
* main: (76 commits) docker-compose update for current version [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release 1.2.1 prepare 1.2.1 version - CHANGELOG.md update green-code-initiative#63 fix: fixes metadata generation task from SonarSource/sonar-update-center-properties correction typo CHANGELOG.md end of 1.2.0 release : change docker-compose to 1.2.1-SNAPSHOT [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release 1.2.0 prepare 1.2.0 version - CHANGELOG.md update prepare 1.2.0 version [ISSUE 177] Rename property in pom (green-code-initiative#177) upgrade CHANGELOG.md [ISSUE 173] correction issue description [ISSUE 161] ➖ Remove unused junit dependency [ISSUE 173] correction of unit tests :( update CHANGELOG update CHANGELOG with recent issues - improve update CHANGELOG with recent issues [ISSUE 173] update description issue (to really describe what the rule does) ... # Conflicts: # python-plugin/src/main/java/fr/greencodeinitiative/python/PythonRuleRepository.java # python-plugin/src/test/java/fr/greencodeinitiative/python/PythonRuleRepositoryTest.java
it would be very useful to add those plugins on the SonarQube Marketplace.
The procedure is relatively straightforward. See: https://github.com/SonarSource/sonar-update-center-properties
If you are OK with this idea, and if you wish, I can do the work for you.
The text was updated successfully, but these errors were encountered: