Goals

1. Add the option to customize the artifacts upload timeout for the remote caching feature, to a different value rather than the statically defined 200 seconds window:

Non-goals

1. Timeout for local tasks: this request is only concerned about the upload timeout for the remote caching feature.
2. Increasing the default upload timeout (200 seconds): instead, provide a way to customize the default.

Background

When using a custom self-hosted server as remote cache, it's possible that the available bandwidth to the custom instance is limited. Moreover, the artifact size can be large enough for preventing the element being uploaded within the statically-configured upload timeout.

Having the possibility to override the default timeout would greatly improve the flexibility of the remote caching feature, allowing to set up custom servers to cache larger artifacts (100MB+) that require minutes to be uploaded.

For reference, users have reported turbo timing out while uploading artifacts on a custom remote cache server:
ducktors/turborepo-remote-cache#407

Proposal

The remote timeout could be configured with an environment variable TURBO_API_UPLOAD_TIMEOUT similar to how the remote cache server can be set up with TURBO_TEAM, TURBO_TOKEN and TURBO_API variables.

Happy to work on the proposed feature if this is approved! 🚀