On 11/24/2013 12:21 AM, Vijay Bellur wrote:
On 11/23/2013 02:02 AM, Lalatendu Mohanty wrote:
On 11/23/2013 01:35 AM, Lalatendu Mohanty wrote:
On 11/23/2013 01:27 AM, Anand Avati wrote:
Lala,
It would be ideal if we hooked this into Jenkins and run along with
regression test in parallel. How feasible is it to set it up that way?
Yup, agree. Will try to find a solution for this. We need a way to
download the result from http://scan.coverity.com and analyse it
through scripts. If anybody already have done it let us know :).
Bummer! . Coverity allows only 4 runs per week for opensource projects
that have lines of code between 100K to 500K and GlusterFS has more than
300K lines of code. Read the faq link below for details.
https://scan.coverity.com/faq#frequency
What should we do now?
Schedule bi-weekly runs? That should be a good start for us.
Agree, will schedule biweekly runs.
For continuous integration, we can probably use clang. There is a
project open on forge for this already:
https://forge.gluster.org/clang-compiled-glusterfs#more
-Vijay
