3 ms·
> 1. You [and tools] don't know where the code is just by inspecting the binary; Your bug reporting tool should obviously report the version of the software th
by beeboobaa3 3y ago
> 1. You [and tools] don't know where the code is just by inspecting the binary;
Your bug reporting tool should obviously report the version of the software the dump is associated with. It's common to just put the git hash in the binary.
> 2. There may be more than one answer to the question relative to what?
The directory CI runs in. If you're not sure, check your CI scripts.
- yosefk 3y ago1. What if the version has uncommitted changes? What if the code is compiled from multiple repositories? I should now clone them all? 2. As discussed in GP, there can be more than one such directory if your build isn't monolithic (which it should be, but it often isn't)
- beeboobaa3 3y ago> What if the version has uncommitted changes How is knowing the filenames going to help with that? > What if the code is compiled from multiple repositories? I should now clone them all? Presumably you already have a CI script that does this. If not, invest a few minutes into making one.
- yosefk 3y agoIf the code has uncommitted changes they are typically (~always) kept in the modified files they were compiled from. Knowing the filenames is how you find them.
- beeboobaa3 3y agoGreat, I now have the path to my git repository, same as every other build, and probably leaked my system username in the process.
- runiq 3y agoThat has been addressed in TFA: https://yosefk.com/blog/refix-fast-debuggable-reproducible-builds.html#why-do-this-we-already-have-a-system-for-finding-the-source-code https://yosefk.com/blog/refix-fast-debuggable-reproducible-b....