-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Minor
-
Component/s: ecs-publisher-plugin
-
None
This is what the plugin provides:

Â
| Allow ECS to break build | ![]() |
|
|  | Allow break build. (from ECS publisher) |
 |
| Manage Break Sensitivity | ||
| Break on vulnerabilities | ![]() |
|
| Break on Vulnerabilities. (from ECS publisher) |
 | |
| Break on legal issues | ![]() |
|
| Break on Legal Issues. (from ECS publisher) |
 | |
| Â | ||
| Â | Â | Â |
| Cloud |
Â
- Help should be helpful. It should not simply restate in nearly identical wording a checkbox item.
- Break isn't commonly used in Jenkins terminology. Jenkins builds typically Fail resulting in Failure}}s or {{Failed builds.
- The way you're managing checkboxes and groups is wrong, please consider this example instead:
 (collapsed)
And (expanded):
Note: please don't feel obligated to waste a column on something like Naming Strategy, that's a bug that I'll fix later.
- If you have documentation about what a "Legal issue" is, and you can't fit it into your help box, then including a link from your help text to your documentation would be incredibly helpful.
