Configuring Compiler warning parser tasks
This feature is a part of the Bamboo 6.7 Early Access Program, which is are snapshots of the ongoing Bamboo development process. For that reason:
- While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
- Features in development releases maybe incomplete, or may change or be removed before the next full release.
Much as you are able to upgrade previous versions of Bamboo to the 6.7 EAP version, and smoothly upgrade from the 6.7 EAP to the final version, once it's released, we don't recommend installing the EAP release on your current production environment. For information about the supported upgrade paths, see Bamboo upgrade guide.
Use Compiler warning tasks to scan build logs and output files for compiler warning. Warnings are aggregated into a build artifact and the summary of the warnings is displayed in the build result page.
To create a Compiler Warning parser task:
- In you job configuration scree, click the Tasks tab.
- From the Builder type group, select Compiler warning parser.
A description of the task, which is displayed in Bamboo.
Disable this task
Check, or clear, to selectively run this task.
Type of parser used by the task. Pick the one that matches the compiler (or other tools) used in previous steps of the build.
Associate warnings with a repository
Warnings can be associated with a repository containing your sources. This information can be later to used to notify the source control system about the amount and severity of warnings found by this task. By default, the warnings are linked to the default repository of the build.
Pick the correct source repository to associate the warnings with.
Where Bamboo should look for warnings. You can choose between parsing the output logs (default) or the file matching a glob pattern.
A glob pattern defining which files should be scanned for compiler warnings.
Fail build if too many warnings are found
Switch this option of causes build to fail if number of warnings exceed defined threshold.
Severity of warnings being counted
The severity level of warnings counting towards build failure threshold. There are 3 severity levels: low, normal and high.
Fail build threshold
If number of warnings (taking into account their severity) exceeds this number the build fails.
Example of a Compiler warning parser task configuration.