Unfortunately I’m not aware of a program at Microsoft to donate build machines to open source projects.
From: Scons-dev [mailto:[email protected]] On Behalf Of Bill Deegan Sent: Friday, July 24, 2015 11:26 AM To: SCons developer list Subject: Re: [Scons-dev] Adding Visual Studio 2015 Support to SCons Rob, Thanks for the patch! Any chance we can convince you to provide a buildbot slave for testing on the windows platform? ;) I'm going to take a look through the remaining pull requests over the next couple days and if any of those look simple I may pull them in and push a new release. Regardless I'd think a new release with this patch should get out in the next couple weeks. -Bill On Fri, Jul 24, 2015 at 1:30 PM, Rob Smith (WINDOWS) <[email protected]<mailto:[email protected]>> wrote: The other pull request was merged and kicked off a new build which passed 100% (I verified this ran the new VS 14 tests): http://buildbot.scons.org/builders/win7-64-vs20102.7/ Looks like we should be good now. -----Original Message----- From: Scons-dev [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Dirk Bächle Sent: Thursday, July 23, 2015 1:27 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Scons-dev] Adding Visual Studio 2015 Support to SCons Rob, On 23.07.2015 18:54, Rob Smith (WINDOWS) wrote: > Looks like the build is exiting immediately because it doesn't find any new > changes: > yes, but it should actually detect that it's not at the latest revision available. Triggering a build manually should not rely on the "hg pull" to emit new changes, because if the update to the "tip" revision was missed last time, it gets missed again and again...until finally a new commit is added to the repository. Another scenario would include a person logging into the build machine and doing a "hg update" on the command line, such that the sources point to a completely unrelated revision! Bill, can we somehow add an "always-update-to-latest-revision" step for the manual trigger? We should be safe for normal commits because we have a corresponding commit ID there, right? Best regards, Dirk _______________________________________________ Scons-dev mailing list [email protected]<mailto:[email protected]> https://pairlist2.pair.net/mailman/listinfo/scons-dev _______________________________________________ Scons-dev mailing list [email protected]<mailto:[email protected]> https://pairlist2.pair.net/mailman/listinfo/scons-dev
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
