JavaScript is not currently enabled, but is required for full
CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable
JavaScript in your browser: you will also need it for GUI
functionality.
If you opened this file directly from disk, your browser may be
directly suppressing JavaScript functionality: certain browsers
perform this suppression on local files (but not files delivered by
web servers) for security reasons.
-
If you access the manual through the hub's Web GUI, the
functionality will not be suppressed because the hub is a web
server.
-
Alternatively, your browser may allow you to explicitly
disable the security setting that suppresses functionality. See
the CodeSonar
FAQ for more information.
Task: Assign All Warnings In A Directory To One User
If your development team is organized so that different users
have responsibility for different parts of the system, it is useful
to be able to assign groups of related warnings to a user in one
big batch, rather than assigning each warning separately. This
operation has two parts:
Suppose you want to assign all warnings in the directory
src/ioutil to Lindsay.
- If the CodeSonar Web GUI is not already open, open it now.
- Sign in. This is necessary because assigning a new Owner to
warnings involves changing the hub database.
- Carry out a search for warnings in the directory src/ioutil:
- Select warnings in all
projects from the search domain/scope menu.
- Enter path:src/ioutil in the search
field.
- Click Search.
- Examine the warning table on the Warning Search
Results page to make sure the contents are what you
expected.
- Click the Change Multiple
Warnings button under the warning table. Additional fields
will appear on the page.
- Click the Check All button to
select all the warnings in the table.
- Select Lindsay from the
pull-down Owner menu (under the
warning table). If Lindsay does
not appear in this list, then either the Lindsay account has been disabled or Lindsay
has not yet created a CodeSonar account. The Administrator user can
enable disabled users. Anyone can create a new account called
"Lindsay" by going to the Sign In page (you must be
signed out first, though).
- Click the Save changes
button.
CodeSonar will display a page that describes the changes
you made and lists the warning reports affected.
The method described above is suitable for
assigning warnings from analyses that have already been
performed.
You can also instruct CodeSonar to assign all warnings
from future analyses to Lindsay if they are in directory src/ioutil. To do this, you will use a WARNING_FILTER rule in the general
template configuration file.
- Open $CSONAR/codesonar/template.conf for
editing.
This is the general template configuration file: it is applied to
all CodeSonar analyses performed with the corresponding
installation. If you only want to assign warnings in one project,
edit the general
project configuration file for that project instead.
- Add the following rules to the template.
WARNING_FILTER += owner:=Lindsay path:src/ioutil
WARNING_FILTER += owner:=Lindsay path:src\ioutil
- Check the other WARNING_FILTER
rules defined in the template to make sure none of them conflict
with your new rules. If you find any, you have two options for
addressing the conflict.
- If you no longer want the conflicting rule, delete it.
- If the conflict is only partial and you want to keep some
of the behavior of the conflicting rule, edit the rule to
remove the conflict.
- Save your changes to the template.
For future analyses with the corresponding CodeSonar
installation, Lindsay will now be established as the owner of
warnings issued in src/ioutil before
the warnings are submitted to the hub.