You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently support extensions from any URL, which are cached in the global cache and downloaded once.
If we extended this concept to arbitrary binaries for tasks, which could be cached and then executed (assuming they have no dynamic linkage requirements), then that would be a nice way around pathing issues for CLI things.
The concept would be to have an architecture matrix that downloads the right URL then associates it with an environment variable in the global cache to reference in a task. This could be pretty cool.
The text was updated successfully, but these errors were encountered:
We currently support extensions from any URL, which are cached in the global cache and downloaded once.
If we extended this concept to arbitrary binaries for tasks, which could be cached and then executed (assuming they have no dynamic linkage requirements), then that would be a nice way around pathing issues for CLI things.
The concept would be to have an architecture matrix that downloads the right URL then associates it with an environment variable in the global cache to reference in a task. This could be pretty cool.
The text was updated successfully, but these errors were encountered: