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
Glad to see people using Attic! This can be tricky until Attic is added to nixpkgs and cached by cache.nixos.org, which is happening soon with the first stable release. I would advise downstream projects to hold off until the release occurs, especially since a rename may be happening.
At my job we use nix-based containers to run the CI/CD jobs. These jobs are built with an own framework called Makes, this tool makes it easier to configure the environment.
We used cachix as the main cache provider, add attic as an additional cache provider for the framework, so jobs would have a local cache and avoid downloading binaries from the internet, but the difference in time that we save using attic is not worth deploying a cache locally. In addition, the upload of the binaries to the attic server is quite slow compared to cachix.
I am importing the package and extracting the attic-client attribute but all attic components are built.
This is the code associated with the import and use of attic-client: fluidattacks/makes@main...drestrepom:makes:main#diff-ecdfd02b8e24dc35996c02b7530266eb6fe5e03239e760490f2839d556c55f06R9
What could be the most optimal way to import it?
The text was updated successfully, but these errors were encountered: