Continuous integration

[mikezackles]

Now that zach has made progress on incorporating autotools to handle the make dependencies, previoulsy handled in eclipse, the project is closer to implementing continuous integration tools.

Identify any remaining issues that must be resolved prior to implementing continuous integration technology.

1. the huge, all-in-one magmad.so build (~380Mb) complicates continuous integration. Sites like github don't allow files that large, so in many (all?) cases, the magmad.so output may have to be recompiled on the fly. Is this enough to drive a need to split up magmad.so? Or better yet, is it time to consider building a release that depends on supporting packages to be installed vs building everything in one supporting .so file?

[mikezackles]

kdh - Added to list in main comments:
magmad.so complicates this as we'll want to avoid rebuilding it unless something changes with the bundled deps.

[kenthawk]

Continuous Integration has been working for over a week on the develop branch in magma.classic. It is being performed using Jenkins and being reported to the slack lavabit channel for both successes and failures!