On 28.02.2012 18:00, Gene Buckle wrote: > Yes. I needed to use the machine.:) > I've re-enabled the MSVC host.
And I just triggered a rebuild for Windows/next. Hope the load stays low... >> > I think the problem is that a build is redone every time fgrun is >> > changed because there is no release branch, and it rebuilds >> > everything because Jenkins touch files when it copies artifacts. >> > >> > One solution could be to split the task : one for building binaries, >> > one for packaging. >> > > One thing I noticed it did is that it built windows-release, built two > other packages and then built windows-release_again_. That's when I got > really annoyed.:) History shows that all rebuilds were triggered for a reason - either due to fgrun changes or due to an update of the installer package itself. But see below... We really should create a separate fgrun/Release job: right now, the fgrun job depends on SimGear/next, though Windows/Release depends on fgrun. So, first of all, the fgrun binary in the Release installer isn't built with the correct simgear DLLs (it's was already build against the simgear/2.7.0 - which luckily/hopefully was still compatible to simgear/2.6.0 at the time of the release) - or am I missing something? Secondly, every SimGear/next change triggers an fgrun rebuild (as expected), but due to the fgrun dependency, it also triggered a rebuild of the Windows/Release job. Seems like we something we should improve :). Also, as suggested by Fred, splitting the (Windows) Release job itself into smaller jobs (simgear/flightgear/installer), makes a lot of sense... cheers, Thorsten ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
