Re: Automating Coverity, was Re: [PATCH 00/26] Address a couple of issues identified by Coverity
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 5, 2017, 20:30 UTC
- Message-ID
- <alpine.DEB.2.21.1.1705052227120.146734@virtualbox>
- In-Reply-To
- <alpine.DEB.2.20.1704282205320.3480@virtualbox>
Hi Stefan,
On Fri, 28 Apr 2017, Johannes Schindelin wrote:
Show 21 quoted lines
> On Fri, 28 Apr 2017, Stefan Beller wrote: > > > On Thu, Apr 27, 2017 at 3:50 PM, Johannes Schindelin > > <Johannes.Schindelin@gmx.de> wrote: > > > > > I still have to find the time to figure out one more detail: how to > > > download and extract the Coverity tool (the .zip archive has a > > > variable name for the top-level directory), and doing that only > > > every once in a while, say, only when there is no previously > > > unpacked tool, or it is already 4 weeks old. > > > > That is an interesting problem, which I ignored as the older versions > > of their tools still works once they release new versions. So I just > > manually check every once in a while if they have new versions out > > there. > > > > So if you find a nice solution to that problem, let me know, please. > > I think I have a working idea (jotting it down in the editor, untested): > > [... totally untested snippet ...]
And now I edited it and tested it. The code is now part of the script I use for pretty much all administrative (i.e. recurring and boring) tasks in the Git for Windows project:
https://github.com/git-for-windows/build-extra/commit/05b5342128
May it be useful to you, too, at least as a starting point, Dscho