Comment 8 for bug 1385229

OK, so Caio figured out why the archiver was failing but we still need to think of whether it makes sense to have a backup archiver of some kind.

Using local storage would be the most reliable solution, the main issue I see is that the capomastro host may not have enough resources to archive locally (otherwise we wouldn't need an external archiver :).

The safest way to implement this would be to somehow declare the amount of local disk space that could be used for failed-archiver backups, and implement a FIFO queue there, so once the space is used up, older backed-up artifacts will be deleted. And we also need to make provisions for people to be able to recover artifacts from within the capomastro UI, thinking that sometimes direct host access is not possible in our deployment scenario.

Ideally, if builds fail to archive, we can be loud enough that artifacts won't get lost in the queue because a developer didn't check on his build status.

I'm triaging this as future as it looks like a slightly larger feature but feel free to move around if it needs to be done sooner.