How do I use InspectCode Command-Line Tool with Unity in CI?
Answered
We are using InspectCode Command-Line for CI.
However, there is a subtle difference between the Rider (with Unity) that we use at hand and the InspectCode Command-Line.
For example, Naming Rule for SerializeField.
Is there a best practice to align these differences in a CI environment without Unity?
Please sign in to leave a comment.
Hello Kyubuns,
Thank you for contacting us! Which OS do you run?
We have both Windows and macOS ready for CI.
Either is fine with me.
Please try to use the Unity extension with InspectCode. The feature is currently available for Windows only, we're going to add it for macOS and Linux in the upcoming releases.
To use the plugin, add the following option to the command line:
The command makes InspectCode download the matching extension version and use it during the analysis.
The Unity extension is usually released later then the regular ReSharper / InspectCode version. So you can use InspectCode 2020.3.4 now. 2021.1 Unity plugin isn't available yet.
Please let me know if using the extension produces the inspection results matching with Rider.
Thanks!!
The problem has been resolved.
(For those who saw it later. I couldn`t get it to work with `-x JetBrains.Unity`, so I downloaded and put nupkg).
Hey, could you please tell how did you put nupkg into macOS dotnet? I'm really struggling with it atm. Is there any way to add nupkg without downloading inspectcode.exe?
Hi Pavel Samsonov
You can try the workaround. I'm afraid, the zip package of Command-line Tools is required for this, not the dotnet installation.
Please note that the scenario isn't supported officially.