Aggregated news from external sources
Static analysis programs are quite useful, but also prone to false positives.
It’s really hard to keep track of static analysis failures on a fairly large
project. We’ve looked at several approaches in the past. The one that we used
to do was to publish a report every day which people could look at if they
wished. This guaranteed that nobody looked at it. Despite knowing where to
look for it, even I barely looked at it.
The second approach was to run them twice, before your patch is merged and
after your patch is merged in. If the count goes up with your patch, the test
fails. This has a problem that it doesn’t account for false positives. An
argument could be made that you could go fix another static analysis failure in
your patch. But that means your patch now does two things, which isn’t fun for
when you want to do a backport, for instance. Or even for history purposes.
That’s landing two unrelated changes in one patch.
The approach that we’ve now gone with is to have them run on a nightly basis
with Jenkins. Deepshika did almost all the work for this and wrote about it on
her blog. It has more details on the actual implementation. This
puts all the results in one place for everyone to take a look at. Jenkins also
gives us a visual view of what changed over the course of time, which wasn’t as
easy in the past.
She’s working on further improving the visual look by uniting all the jobs that
are tied to static analysis. That way, we’ll have a nightly pipeline run for
each branch that will put all the tests we care about for a particular branch
in one place.
Source: nigelb (Static Analysis for Gluster)
In order to plan the content for upcoming releases, it is good to take a moment of pause, step back and attempt to look at the consumption of GlusterFS within large enterprises. With the enterprise architecture taking large strides towards cloud and more specifically, the hybrid cloud, continued efforts towards...
The Gluster community is pleased to announce the release of 7.0, our latest release. This is a major release that includes a range of code improvements and stability fixes along with a few features as noted below. A selection of the key features and bugs addressed are documented in this...
Progress cannot be made without change. As technologists, we recognize this every day. Most of the time, these changes are iterative: progresssive additions of features to projects like Gluster. Sometimes those changes are small, and sometimes not. And that’s, of course, just talking about our project. But one of the...