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
{{ message }}
This repository has been archived by the owner on Feb 28, 2021. It is now read-only.
Changes to, say, the README file will trigger a complete new build. We want to explore ways of caching the binaries and only rebuild them if the targets composing it have changed. For example, if a commit changes the CLI alone, only the CLI should be rebuilt and not the whole project and the node binary.
The text was updated successfully, but these errors were encountered:
The caching works pretty well on a local machine because it uses timestamps. If you update only the CLI and rebuild cargo can figure out that only the CLI changed and rebuild only that. On CI this information is not available through timestamps though since we do a fresh checkout at the start of the build. I don’t have an idea for a solution to this.
Unfortunately you're right, files are fingerprinted with their date and not with their content. Hopefully at some point it may change: rust-lang/cargo#6529
Is there something actionable in the ticket? If the cargo issue is solved we basically get this for free. Unless we have other options I’d vote to close this.
Changes to, say, the README file will trigger a complete new build. We want to explore ways of caching the binaries and only rebuild them if the targets composing it have changed. For example, if a commit changes the CLI alone, only the CLI should be rebuilt and not the whole project and the node binary.
The text was updated successfully, but these errors were encountered: