Artifacts cannot be retrieved from timed out jobs

  1. If trying to pull artifacts from a job that terminated with ERROR: Job failed: execution took longer than xxx seconds, you get a status 500 from API (they are also absent from UI), even though the artifacts are set to be stored "always".
  2. The message itself is formatted incorrectly: 10h0m0s seconds -- this is not how it is supposed to work.
  3. The logs from timed out job are only available in UI, but not through API, again, due to server errors.
  4. I've filed and refiled this issue: it is absolutely wrong not to have "infinite" jobs. More so, "infinite" should be the default for the program. And if you want your own runners to do differently (for financial reasons), then your default runner configuration must contain a different value.
  5. There's no notification mechanism for the script running in CI about it being terminated due to timeout.

Bottom line, the timeout functionality is thoroughly broken. Please do it over. It just too dysfunctional and disappointing as it is now.

Edited Apr 17, 2019 by Oleg Sivokon
Assignee Loading
Time tracking Loading