Hello, it has now been almost 2 months since we started setting up the first jobs on Jenkins and I want to thank you all.
Out of 750 builds (the last 50 of each job) only 2% actually failed which I think is really great. We are currently building efl, elm and e on 32 and 64-bit Linux both with gcc and clang. Furthermore, clang has the address sanitizer feature enabled which means that tests abort if it detects invalid memory access/buffer overruns, etc. After some issues with the build setup itself we found quite a few existing issues with the help of address sanitizer and also caught new issues that were being introduced (cedric, I'm looking at you! :-). So a big thank you for testing your commits and also for caring about broken builds and fixing the issues that arose. In addition to the jobs running for every SCM change there are now also nightly builds for efl, elm and e. These builds publish docs, coverage information and results of the static analyzer scan-build. You can get to this information by following the links on the left side of http://build.enlightenment.org/ But there's still lots of things that we can improve: * Create jobs that build dev/user/jenkins branches (automagic build-your-own-branch) so we can test *before* if all those tests still work * Neither Enlightenment nor Elementary have actual tests. Tom is working to get exactness in shape right now so we should be able to change that pretty soon and get tests and coverage at least for Elementary. * Coverage for EFL is pretty low. There are some highlights like Eo and eet, but most other parts have a coverage of less than 60% - many are around 10%. Eio, eldbus and evas could all use some love in that regard. See https://build.enlightenment.org/job/nightly_efl_gcc_x86_64/lastSuccessfulBuild/Coverage_information/? * We're not building branches - yet. This should be easier once 1.8 is released as we don't have to build 10 different libraries. If you want to help with anything specific or if you have other issues with the current setup please let me know. Regards, Daniel ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
