I have two related requests regarding how the artifacts are copied, assuming that no proper syncing will be implemented any time soon:

1. The copying process when archiving artifacts should impose a timeout on network operations. If nothing has been sent for some period of time, it should break the connection. What happens now is that when the connection stalls, our builds run forever or until someone cancels it manually.

2. When copying fails, it should retry (perhaps after waiting a moment.) This plays well with the timeout because it means that when a timeout occurs, the copy fails and gets retried.

Remember, the first fallacy of distributed computing is "The network is reliable." So you can't assume a single attempt to copy the data will always work.