Automatically disable build triggers with successive failures or internal errors

We allow users to reenable them manually once disabled
This commit is contained in:
Joseph Schorr 2017-10-18 16:03:38 -04:00 committed by Joseph Schorr
parent c35eec0615
commit 93d79e777e
9 changed files with 166 additions and 11 deletions

View file

@ -169,16 +169,27 @@
</td>
</tr>
<tr class="trigger-disabled-message" ng-if="!trigger.enabled">
<td colspan="5" style="text-align: center">
<td colspan="5" style="text-align: center"
ng-if="trigger.disabled_reason == 'user_toggled'">
<i class="fa fa-exclamation-triangle"></i>
This build trigger is currently disabled and will not build:
This build trigger is user disabled and will not build:
<a ng-click="askToggleTrigger(trigger)">Re-enable this trigger</a>
</td>
<td colspan="5" style="text-align: center"
ng-if="trigger.disabled_reason == 'successive_build_failures'">
<i class="fa fa-exclamation-triangle"></i>
This build trigger was automatically disabled due to successive failures:
<a ng-click="askToggleTrigger(trigger)">Re-enable this trigger</a>
</td>
<td colspan="5" style="text-align: center"
ng-if="trigger.disabled_reason == 'successive_build_internal_errors'">
<i class="fa fa-exclamation-triangle"></i>
This build trigger was automatically disabled due to successive internal errors:
<a ng-click="askToggleTrigger(trigger)">Re-enable this trigger</a>
</td>
</tr>
</tbody>
</tbody>
</table>
</div>
</div>
</div> <!-- /Build Triggers -->