https://bugzilla.redhat.com/show_bug.cgi?id=1395212
--- Comment #2 from Nigel Babu <nig...@redhat.com> --- First set of changes to run the staticanalysis builds on the cage infrastructure: https://github.com/gluster/gluster.org_ansible_configuration/pull/14 I've got a job to run cppcheck on a nightly basis for master at the moment: https://build.gluster.org/job/cppcheck/ Step 1: Get a Jenkins job for everything. Step 2: Step up analysis.rht.gluster.org ready for serving the static files. Step 3: Use Jenkins-based automation to move the logs into staticanalysis.rht.gluster.org That's stage 1, so we're using the current workflow but automated with jenkins. We'll figure out what stage 2 looks like in the future when things settle down, whether it's double compilation or analyzing increase vs decrease of the number. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LlLl9xrBQj&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra