Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #19 from mixalturek/master
[JENKINS-23891] Redesign of configuration page
- Loading branch information
Showing
7 changed files
with
144 additions
and
151 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 0 additions & 7 deletions
7
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/config.properties
This file was deleted.
Oops, something went wrong.
12 changes: 12 additions & 0 deletions
12
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/help-pattern.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
<p style="margin-top: 0px;">Cppcheck must be executed to generate XML reports for this plugin to function. | ||
<a href="http://ant.apache.org/manual/Types/fileset.html">Fileset | ||
'includes'</a> setting specifies the generated Cppcheck XML report files, | ||
such as '**/cppcheck-result-*.xml'. Base directory of the fileset is relative | ||
to the workspace root directory.</p> | ||
|
||
<p>If no value is set, then the default '**/cppcheck-result.xml' will be used. | ||
Be sure to never include any non-report files into this pattern.</p> | ||
|
||
<p>The plugin is able to work with both XML formats produced by Cppcheck, | ||
but always prefer to use the newer version 2. Cppcheck doesn't report some | ||
issues with the legacy format.</p> |
2 changes: 2 additions & 0 deletions
2
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/help-severity.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
Determines which severity of issues should be considered when evaluating the | ||
build status and health. |
4 changes: 4 additions & 0 deletions
4
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckPublisher/help-thresholds.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
Configure the build status and health. A build is considered as unstable or | ||
failure if the new or total number of issues exceeds the specified thresholds. | ||
The build health is also determined by thresholds. If the actual number of | ||
issues is between the provided thresholds, then the build health is interpolated. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,18 @@ | ||
description.threshold=If the total number of errors exceeds this threshold then a build is \ | ||
considered as unstable. Leave this field empty if the unstable state of the build \ | ||
should not depend on the total number of errors. | ||
description.newThreshold=If the number of new errors exceeds this threshold then a build is \ | ||
considered as unstable. Leave this field empty if the unstable state of the build \ | ||
should not depend on the number of new errors. | ||
description.failureThreshold=If the total number of errors exceeds this threshold then a build is \ | ||
considered as failed. Leave this field empty if the failed state of the build \ | ||
should not depend on the total number of errors. | ||
description.newFailureThreshold=If the number of new errors exceeds this threshold then a build is \ | ||
considered as failed. Leave this field empty if the failed state of the build \ | ||
should not depend on the number of new errors. | ||
description.healthy=Report health as 100% when the number of errors is less than this value. | ||
description.unhealthy=Report health as 0% when the number of errors is greater than this value. | ||
|
||
description.status=Configure the build status and health. A build is considered as unstable or failure \ | ||
if the new or total number of errors exceeds the specified thresholds. \ | ||
The build health is also determined by thresholds. If the actual number of errors is between \ | ||
the provided thresholds, then the build health is interpolated. | ||
|
||
|
||
|
||
description.limit=Determines which severity of errors should be considered when evaluating the build status and health. | ||
|
||
description.threshold=If the total number of issues exceeds this threshold then a build is \ | ||
considered as unstable. Leave this field empty if the unstable state of the build \ | ||
should not depend on the total number of issues. | ||
description.newThreshold=If the number of new issues exceeds this threshold then a build is \ | ||
considered as unstable. Leave this field empty if the unstable state of the build \ | ||
should not depend on the number of new issues. | ||
description.failureThreshold=If the total number of issues exceeds this threshold then a build is \ | ||
considered as failed. Leave this field empty if the failed state of the build \ | ||
should not depend on the total number of issues. | ||
description.newFailureThreshold=If the number of new issues exceeds this threshold then a build is \ | ||
considered as failed. Leave this field empty if the failed state of the build \ | ||
should not depend on the number of new issues. | ||
description.healthy=Report health as 100% when the number of issues is less than this value. | ||
description.unhealthy=Report health as 0% when the number of issues is greater than this value. | ||
|
||
severity.evaluation=Severity evaluation | ||
|
||
graph.configuration=Graph configuration | ||
graph.description=Check severity category to display in the graph | ||
|
||
|
||
|
||
|
||
|
||
|
||
|