How to exclude target paths using an existing IntelliJ IDEA inspection profile

[Tereo725]

Hey,

i know it's possible to exclude paths with a qodana.yml like this:
version: "1.0"
exclude:

• name: All
  paths:
  • relative/path/to/your/file.kt

And it's possible to add a custom profile to exclude all target folder like this:
name: "Excluded target folders"
baseProfile: qodana.recommended
inspections:

• group: ALL
  ignore:
  • "scope#file:**/target//*"

Is there a way to use the IntelliJ IDEA inspection profile instead of a qodana.yml or custom profile as a ruleset and exclude specific file path and e.g. all target folder?

[brichbash]

Hi,

You can use your IDEA profile and set the required scope in a yaml profile that extends your profile.
For that, your IDEA xml profile should be stored under your project root in .idea/inspectionProfiles/, and you should create a yaml profile with the following content:

name: "Excluded target folders"
baseProfile: <your-idea-profile-name>
inspections:
  - group: ALL
    ignore:
      - "scope#file:**/target//*"
      - <scope-2>

You could also avoid using the yaml profile by creating a shared scope in IntelliJ IDEA , setting the scope for required inspections in your profile and then keeping the generated files under .idea/scopes & .idea/inspectionProfiles in your repository. After that, you can apply this profile in Qodana.

[Tereo725]

I created a xml profile My_Ruleset.xml via IntelliJ, and stored it under my project root in .idea/inspectionProfiles/ and i created a profile.yaml with the following content:

name: "Excluded target folders"
baseProfile: My_Ruleset
inspections:
  - group: ALL
    ignore:
      - "scope#file:**/target//*"

Do i still need a qodana.yaml if i want to use it locally via docker or via CI/CD in our gitlab repo?
With our previous ruleset, we used a qodana.yaml with all inspection and exlude rules in it and a CI/CD-Step with a script like this:
qodana --save-report --results-dir=$CI_PROJECT_DIR/qodana --report-dir=$CI_PROJECT_DIR/qodana/report --property=idea.log.config.file=debug.xml --fail-threshold 5

Do i have to change my CI/CD steps for qodana? Where do i have to refere to the profile.yaml? Or does this part stay the same and I write in the Qodana.yaml something like this:

profile:
  path: relative/path/in/your/project/profile.yaml

[Tereo725]

Perhaps it would help if I explained what the exact plan is. We use Qodana within our CI/CD in GitLab for code quality control. We would like to have an across-the-board ruleset that we can use in IntelliJ as well as in GitLab. One for everything, so to speak. We would then use this ruleset as the default ruleset in IntelliJ and have exactly the same feedback in every GitLab build.

[brichbash]

Do i have to change my CI/CD steps for qodana? Where do i have to refere to the profile.yaml? Or does this part stay the same and I write in the Qodana.yaml something like this:
profile:
path: relative/path/in/your/project/profile.yaml

You can either set a path to the yaml profile in qodana.yaml or you can do it by adding the flag --profile-path to your script, it's up to you. Your exclude rules from qodana.yaml will still work.

We would like to have an across-the-board ruleset that we can use in IntelliJ as well as in GitLab.

In this case, creating a shared scope(s) and using it in your inspection profile should suit you better. You can configure scopes for each inspection or group of inspections, please refer to the links I left in the previous comment. Using this approach, your team will have the same inspections in their IDEs as in your pipelines in Qodana.