4 ms·
Just to spare anyone the time: When they say "reproducible" they mean "can be done again" and not "can be done again with a consistent result". No lockfiles, n
by hobofan 3y ago
Just to spare anyone the time: When they say "reproducible" they mean "can be done again" and not "can be done again with a consistent result".
No lockfiles, no checksums, URLs that may disappear and change at any time strewn around everywhere. There is none of the many nowadays common mechanisms in place that would ensure reproducibility (as the term is used in other build systems like Bazel or Nix).
- mieubrisse 3y agoHey hobofan, one of the founders here. You're very correct - we don't have lockfiles yet! It's on our roadmap, but we haven't built it yet because the current level of reproducibility has been enough for our users right now (who are mostly dev and test). That said, if we're to accomplish our goal of being the single platform across dev, test, and prod, lockfiles are an absolute must (we've actually been contemplating whether we can leverage Nix or Bazel under the hood). The design puzzle we've been working on is, how to enable non-determinism and flexibility in dev (e.g. "I want to always use 'latest' on my local machine"), and complete rigidity in prod. I'd guess that we'll have fully reproducible builds available in the next 3 months :)