[guardian-dev] libsqlfs/IOCipher and automated testing

[Abel Luck]

Hans-Christoph Steiner:
> 
> So Abel and I have worked out a working process for IOCipher and
> libsqlfs and we've been working on adding thorough testing, and of
> course making the code pass the tests ;).
> 
> I've been setting up Jenkins to automate the whole process of running
> all these tests, and adding some additional tests.  I just threw in
> cppcheck and valgrind to see if the Jenkins reports are useful.
> 
> We also have been working out of separate repos, then reviewing each
> other's code before pushing commits to the master repo.  The master
> repos are the same:
> 
> https://github.com/guardianproject/libsqlfs
> https://github.com/guardianproject/IOCipher
> https://github.com/guardianproject/IOCipherTests
> 
> And Abel and I (eighthave) have been working from here:
> 
> https://github.com/abeluck/libsqlfs
> https://github.com/abeluck/IOCipher
> 
> https://github.com/eighthave/libsqlfs
> 
> .hc

Yup, this process has been working well enough. Obviously it doesn't
scale well beyond a couple developers. Ideally I'd like to see a more
automated + centralized workflow (e.g., Jenkis CI feeding into Gerrit
review panel)

~abel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 630 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20120830/3f449ba9/attachment.pgp>