Distinguish builds which failed for environmental reasons?

Lilith River's Avatar

Lilith River

09 Oct, 2014 08:13 PM

Many builds fail for environmental reasons (Github is slow or down, Chocolatey, etc). These are typically easy to detect by scanning the last few lines of the console for known error messages, such as "fatal: The remote end hung up unexpectedly".

Perhaps we could define "environment failure messages" in appveyor.yml to identify and distinguish failed code from failed downloads.

These 'build incomplete' jobs could then be colored differently in the console and badges, or perhaps rerun once more after a certain time interval (with a priority of lowest, of course).

  1. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:49 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac