This panel provides settings for managing exclusion templates. These templates can be used as follows:

When delivering code

Onboarding with Fast Scan

When using the Application - Overview with Fast Scan panel after having delivered source code and before starting an analysis:

When editing an existing version

When editing an existing version in the Version Management screen in Application - Versions:

Creating a template allows you to define the folders or files types that should always be excluded (any excluded items will be ignored during the source code analysis). You can then re-use a template each time you deliver source code. One template will be provided out of the box called "default" as shown below (this cannot be edited nor deleted). This template will exclude the following items:

  • target/ (folder
  • temp/ (folder)
  • tests/ (folder)
  • *test (file)
  • tmp/ (folder)
  • .svn/ (folder)
  • .git/ (folder)

Use this option to create a new exclusion template. The following dialog box will be displayed allowing you to create the exclusions you require:

The pattern matching system uses glob patterns (see for examples of how this system works). Enter an expression to match the folders you want to exclude and then press ENTER to add the expression to the list of excluded items.

For example:

  • *.txt will exclude all files with the extension .txt
  • tests/ will exclude any folders named tests and everything inside them - e.g. root_folder/tests, root_folder/another_folder/tests
  • *.Tests/ will exclude any folders whose name includes .Tests (for example C:\Support\Delivery\Sample.Tests\sample\)
  • patterns starting with / will exclude starting only from the root folder. In other words, /tests/ will exclude everything in the specific folder root_folder/tests but not root_folder/another_folder/tests

Click to edit the selected template. You cannot edit the predefined template called default.

Click to delete the selected template. You cannot delete the predefined template called default. Note also that deleting a template that you have already used in a source code version will mean that when delivering a new version none of the exclusions provided in the deleted template will be actioned.