I agree, and I think I can speak for the CipherShed Security Team when I say that automating builds, and automating more testing, is a top priority. Simpler, well documented and reproducible builds was requested by the Audit, and we intend to address all of the issues for which the Audit was able to suggest near-term solutions. While plans could change, currently the plan is to quickly release a rebranded version (once it passes testing to our saticefaction), and then to do a small change to incorporate the near-term solutions suggested in the audit.
Members of the CipherShed team are trying to automate builds of the rebranded executables for Windows now. I think Linux is done, short of bug-fixing and testing, at least for certain flavors. We still need help with Mac, since we only have one generous contributor on that platform, and it may fall behind the others which have more volunteers.
One issue is the old Visual C compiler that is required. As described here, people still recommend using a 1.5X version of Visual C from the early 1990's. This complicates life for everyone trying to verify our builds, but it sounds like we have to live with this for some years to come, while we develop a UEFI boot loader and the world retires it's BIOS-only machines.