Hello. After switching to git push notifications and removing the x32 builds this is the next step of our QA tools consolidation.
Scan-build is a small tool which uses the static analysis functionality coming with clang. We have it running on Jenkins almost from the beginning but due to the many false positives and limited functionality of dealing with defects (it just generates a static html page) people never really jumped on it. The efl build was actually disabled since end of 2014 as we experienced some problems and it was never turned back on. https://build.enlightenment.org/job/nightly_elm_clang_x86_64/lastSuccessfulBuild/artifact/scan-build/build/ https://build.enlightenment.org/job/nightly_efl_clang_x86_64/lastSuccessfulBuild/artifact/scan-build/build If anyone wants to run this on our code it can still be done manually on your local host, but I see no benefit of having it on Jenkins and running every night (at least for elm). If you disagree speak up now as I'm going to remove it from Jenkins next week if nobody complains. regards Stefan Schmidt ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
