Re: [Flightgear-devel] 2.12 is branched

[James T. <zak...@ma...>]

On 21 Aug 2013, at 15:28, Stuart Buchanan <stu...@gm...> wrote:

> On a related note, once the build problem is resolved, could we
> generate a full installation RC package for testing?  It would make it
> easier for testers not familiar with Git to use it, and would be quite
> handy for people like myself who do their development on Linux, but
> have Windows systems available for testing but without the git
> infrastructure or the time to download the entire git fgdata
> repository.

Once the build is fixed, Jenkins should do exactly that - that's part of the automation work I did for 2.10 - Jenkins will produce the complete install EXE, someone just has to grab it from Jenkins and upload / mirror / seed it as they see fit.

Of course, Jenkins only does what it's told by the scripts (mostly in fgmeta besides the CMake files) - so we're still at the mercy of missing files in the installer description and so on - I didn't yet automate a 'smoke test'[1] on Jenkins, since that would mean keeping a clean environment to run test installs, and involve several expensive operations since we'd be launching the sim. That's all doable but requires VMs and more energy than I have. In general I've been hoping to get enough people using the nightly builds that an automated smoke-test would be unnecessary but that's probably optimistic :)

James

[1] 'where there's smoke there's fire', this is old terminology from the Netscape/Mozilla TinderBox engine.