Hello, given the recent incident with [0] I think it would make a lot of sense for the OpenSSL project to have some kind of continuous integration system in place, in order to catch similar problems more quickly.
The easiest way would probably be to enable Travis CI [1] for the GitHub
repository, so that every time something is pushed to it, a test build is
automatically started.
I created a pull request with an initial travis configuration for the openssl
repository at [2]. Among other things it supports building with both gcc and
clang on Linux and OS X (but the latter needs to be enabled manually by the
Travis team) and supports multiple build configurations ("vanilla", "--debug"
and "shared", more can be easily added).
You can see an example build run at [3].
Travis has some limitations though, like the fact that it only supports Linux
and OS X, with fairly old compiler versions (e.g. gcc 4.6). So it might make
sense to build an openssl-specific CI system (e.g. based on Jenkins [4]) but
that would require a lot more work, so enabling Travis CI is IMO the way to go
for now.
Thoughts?
Cheers
[0]
https://github.com/openssl/openssl/commit/25efcb44ac88ab34f60047e16a96c9462fad39c1
[1] https://travis-ci.org/
[2] https://github.com/openssl/openssl/pull/373
[3] https://travis-ci.org/ghedo/openssl/builds/76612407
[4] https://jenkins-ci.org/
signature.asc
Description: Digital signature
_______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
