Support & Status of Perforce Plugin

Hi! :grin:

Currently, the Perforce plugin ( is not working for SonarQube 7.4.
According to the plugin version matrix (, the plugin is incompatible starting with version 7.3.

Is there a possibility that the plugin will be supported for the current (and upcoming) SonarQube releases?

Thanks for your help!

Hey there,

This plugin was deprecated by SonarSource some time ago and moved into our SonarQubeCommunity repo. Nobody is currently maintaining it, and it makes use of APIs that are no longer in the most recent versions of SonarQube.

If you are looking for a side-project, feel free to ask about adoption. :slight_smile:



1 Like

May I ask why is it deprecated? Perforce is still a valid SCM tool. Big companies use it for better or worse (like mine). I’m trying really hard to sell our organization on SonarQube (instead of Coverity–yuck) and Perforce support will be an issue (along with Groovy support).

If perforce is no longer supported, is there recommended way to still use SonareQube 7.6 if we use Perforce?

As for the plugin, it seems others have been submitting pull requests to enable support the new APIs and fix issues. Is the only way to get those changes merged or the plugin updated is to get a new maintainer? It seems that SonarSource employees would be best suited to make sure the pull requests or source changes will work with the new SonarQube APIs.


1 Like

Hello @dh3008 ,

we also use Perforce and faced the same compatibility problem. After a request from my colleagues I upgraded P4 plugin to be compatible with SonarQube 7.4. It’s been used for a while in our projects.

I’ve submitted the code in a PR on GitHub:
However, since the project is not being maintained, the PR can’t be merged.

@ColinHMueller what do I have to do to get the updated plugin adopted? Just publish a post - in the way it is done here, for example? [NEW RELEASE] Ansible Plugin 2.1.0

1 Like

As noted by my colleague @ganncamp

I believe Ann takes it from there. :slight_smile:

Quick note: you will need to make sure the plugin meets all the requirements for Deploying to the Marketplace (and if you could make sure it’s compatible with v7.7 of SonarQube, that would warm my heart :slight_smile: )



OK, I will do my best :slight_smile:


Hello @ColinHMueller ,

sorry for being out of touch so long. I’ve read the requirements for deploying a plugin. And the main thing I can’t figure out at the moment - is how to merge my pull request into the sonar-scm-perforce repository. Only those with write access to this repository can merge pull requests. As far as I understand, the owners of the repository abandoned the project long time ago. But they did a great amount of work and most of the requirements for deploying a plugin are already implemented in this repository. So I’m not sure if it would be a good idea to migrate this project to another repository where I have write access and can merge my upgrade.

Any suggestions / ideas how to deal with this situation are welcome. Unfortunately, I am new to the plugin development, no prior experience with “how it is normally done the right way” :slight_smile:

1 Like