There is a community license, which includes a subset of their supported languages.
https://www.jetbrains.com/help/qodana/pricing.html#license-c...
Must admit this seems like a very odd way of doing it, to me. Normally JetBrains are pretty decent at supporting OSS endeavours.
At present, OSS Java libraries can use Qodana Community, but OSS .NET libraries can't.
Re:
by suumcuique on Friday April 05, 2024 @06:14PM
(#39947915)
If you are running an OSS project you can request a free license for their premium tools: https://www.jetbrains.com/community/opensource/#support
Re:
by Denvercoder9 on Friday April 05, 2024 @06:10PM
(#39947868)
Qodana Community for .NET is currently in Early Access: https://www.jetbrains.com/help/qodana/qodana-dotnet-communit...
They already have a free for OSS you can get which gives you everything as far as I know. https://www.jetbrains.com/community/opensource/#support
How long does that CI job take to run, roughly?
Re:
by albertzeyer on Friday April 05, 2024 @06:27PM
(#39948041)
It's a quite big project (maybe 100k-200k lines, not sure), takes about 10 minutes or less on the GitHub Action node I get, which is not so fast.
It's completely from scratch through the whole project, every time. Maybe I could do it more cleverly and cache the last state somehow and only check changes files or so. But I wanted to keep that logic simple.
Note, I basically have scripted the same functionality as Qodana for our CI, but using the already existing capabilities of the IDE: https://github.com/rwth-i6/returnn/blob/master/tests/pycharm...
This script generates exactly the same warnings as the IDE does.
It downloads some PyCharm Community version and installs it.
It uses the bin/inspect.sh tool which is provided by the IDE.
The IDE bin/inspect.sh needs an existing PyCharm project (all the XML files etc), so this script creates the project files automatically.
This also needs the Python stubs, so this script can create those as well, in the same way the IDE would create them, or alternatively it can download them (I created them in advance for some PyCharm versions).
But then, bin/inspect.sh does not generate all the warnings you see in the IDE. The IDE additionally runs pycodestyle, and so I do the same in the script.
So, as you see, it took a bit of effort to get to all that within the CI, but now it works and I get the same warnings as in the IDE.