tomasbjerre
commented
3 years ago My intention is to always support latest long term support -version of Jenkins. That is my ambition and I don't really have the time/motivation to put more effort into that.
The test-cases run with this version: https://github.com/jenkinsci/violation-comments-to-gitlab-plugin/blob/master/pom.xml#L13
During development I usually smoke test with this version: https://github.com/jenkinsci/violation-comments-to-gitlab-plugin/blob/master/run.sh#L3
And if it does not work for you, I recommend the command line tool: https://www.npmjs.com/package/violation-comments-to-gitlab-command-line I think that is the better choice because you get a solution that you can test locally. Also if you migrate from Jenkins you can still use that command line tool.
You may also want to fiddle with Codeclimate-reports. I never tried it but it sounds like it gives nice feedback in Gitlab. You can transform any static analysis reports to Codeclimate format with this tool: https://github.com/tomasbjerre/violations-command-line Se also https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#implementing-a-custom-tool
We have an quite old version of Jenkins that we had problems upgrading since we also need to update plugins. It would therefore be a nice fact to be able to read in the README.md what versions of Jenkins that are able to handle the plugin. For my needs it is sufficient to know about the latest version but if you want to put some extra sugar on top you make a list where the requirements are changed over time.
Our version of Jenkins is 2.138.