[Bf-committers] Branch merging and buildbot - propose to change build cycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, With the recent amount of branch merging and the amount of post-fixing it generated, some of it due to different platforms in use by developers I'd propose to change buildbot to build more often, even on per-commit basis. This would allow developers to see pretty easy how their work behaves with all necessary logs available. We know that many developers turn of lots of features while working on their own beautiful little garden, sometimes resulting in clipping of nice flowers from other developers (blenderplayer, cross-platform code, etc.). Buildbot is running very well currently and gives useful output, but for developers the nightly cycle can be too long to wait for. Changing to build-on-change will make buildbot much more useful. Buildbot output should become mandatory part of toolset of developers, with the proposed change it will make actually sense too. /Nathan ps. right now linux builds both failed due to navmesh code ( http://builder.blender.org/grid ) - -- Nathan Letwory Letwory Interactive | Studio Lumikuu http://www.letworyinteractive.com | http://www.lumikuu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObaKIAAoJEKtfN7KsE0TtnUcIAKdyAFUyEUWKg1BjcjsrKNTb pGwvSEJXB/31Afu2LddMosMVVhQO5pEyUpKEwdol2EVqdNeVl88Jto7m/sP9OJUi ILe8UXrabSyHzOWtiJR0kCsAt83XVsJ+ztL1ijCw27K0Q2kJvAjKLM3GF1/7vrFl taWZg3SWTEPvQXBJhkJE2thT+EzJ9pwlk0ADEaZCwFKep18bA+TZroMvugmT166f EMGH046UNhZ4VroL54WUETLNYboCjSspAtZXtPo2NLadLWgMUdDLgAclw5YKUXnz TeJvfI/d822OUAnZeaBwp/zgsZTZRVLX62jU5Gk6v/s9/lZSrHP4BWJxYFoUydQ= =f4VP -END PGP SIGNATURE- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Branch merging and buildbot - propose to change build cycle
Hi, Not sure having this behavior always is nice. It's not really needed when you aren't merging and when you're doing merge, you can trigger re-build easily. And there's no need to rebuild Windows build when you're solving issues with Linux platform. About linux slaves.. Looks like there's no version of qsort with one additional argument to callback (like qsort_r and qsort_r) in older versions of libc. We've got two occurrences of this call - one in our navmesh_conversion.cpp and another in recast library. This function isn't used in current raycast svn and i think it can be easily replaced with own implementation of qsort for navmesh_conversion.cpp. Btw, why we've got C++ source in blenkernel? I heard it's because of recats is writtein in C++. But in this case we're writting C-API and storing it in extern/library/library_C-API.c. Nathan Letwory wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, With the recent amount of branch merging and the amount of post-fixing it generated, some of it due to different platforms in use by developers I'd propose to change buildbot to build more often, even on per-commit basis. This would allow developers to see pretty easy how their work behaves with all necessary logs available. We know that many developers turn of lots of features while working on their own beautiful little garden, sometimes resulting in clipping of nice flowers from other developers (blenderplayer, cross-platform code, etc.). Buildbot is running very well currently and gives useful output, but for developers the nightly cycle can be too long to wait for. Changing to build-on-change will make buildbot much more useful. Buildbot output should become mandatory part of toolset of developers, with the proposed change it will make actually sense too. /Nathan ps. right now linux builds both failed due to navmesh code ( http://builder.blender.org/grid ) - -- Nathan Letwory Letwory Interactive | Studio Lumikuu http://www.letworyinteractive.com | http://www.lumikuu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObaKIAAoJEKtfN7KsE0TtnUcIAKdyAFUyEUWKg1BjcjsrKNTb pGwvSEJXB/31Afu2LddMosMVVhQO5pEyUpKEwdol2EVqdNeVl88Jto7m/sP9OJUi ILe8UXrabSyHzOWtiJR0kCsAt83XVsJ+ztL1ijCw27K0Q2kJvAjKLM3GF1/7vrFl taWZg3SWTEPvQXBJhkJE2thT+EzJ9pwlk0ADEaZCwFKep18bA+TZroMvugmT166f EMGH046UNhZ4VroL54WUETLNYboCjSspAtZXtPo2NLadLWgMUdDLgAclw5YKUXnz TeJvfI/d822OUAnZeaBwp/zgsZTZRVLX62jU5Gk6v/s9/lZSrHP4BWJxYFoUydQ= =f4VP -END PGP SIGNATURE- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Branch merging and buildbot - propose to change build cycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.9.2011 9:27, Sergey I. Sharybin wrote: Hi, Not sure having this behavior always is nice. It's not really needed when you aren't merging and when you're doing merge, you can trigger re-build easily. And there's no need to rebuild Windows build when you're solving issues with Linux platform. Indeed, but it happens regularly that builds break on different platforms, and even more so because developers *don't build with all features enabled* (while in theory they should always verify the entire build before doing any commits). Sure, triggering manually is a way, but it is even better to not have to do that. Developers are lazy beings (hence they are developers). With the amount of developers that we have commiting I think its especially nice if our buildslaves would just build the moment they don't have anything to do and are notified of changes. /Nathan - -- Nathan Letwory Letwory Interactive | Studio Lumikuu http://www.letworyinteractive.com | http://www.lumikuu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObbw4AAoJEKtfN7KsE0TtBkwH+wTA5skYb86CIeEN3VqEW8xs 8Jzorq4Ip4ySfrsbv8v1HDKcHNJvQzO0SmWHYD7KPunwqsFFquqXc3iIEFoG+43B xvDsA/paFxE6iz6AzpzqIvP4oMHL1YJXnokiBdxrGf+Go6RFehKKkTFY4UfHLH+7 OpvPYQk/zdEMCjG5Yz8lv7WFzjPwzaVPLFCkXH5HFFfRgnY2OjEoO0wlJXsUTISu c4aqqXWSOHQmFrHdCdKvVVU3v16Gqpryi2S5J2ghU1onzimTvApGiIcTWVru/rNU bUrMgY8Cacs1Jl4OkOEzTybZnnxJWrYM7SMWHjWAFbwsZBGwwft8rQaj1NsJ43I= =YPMf -END PGP SIGNATURE- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Branch merging and buildbot - propose to change build cycle
Hi, Nathan Letwory wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Indeed, but it happens regularly that builds break on different platforms, and even more so because developers *don't build with all features enabled* (while in theory they should always verify the entire build before doing any commits). Sure, triggering manually is a way, but it is even better to not have to do that. Developers are lazy beings (hence they are developers). With the amount of developers that we have commiting I think its especially nice if our buildslaves would just build the moment they don't have anything to do and are notified of changes. Well, just triggering isn't enough. It wouldn't make developers check buildbot logs, IMO. It should also punish developers who breaks something. Or at least notify them. -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Branch merging and buildbot - propose to change build cycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.9.2011 12:01, Sergey I. Sharybin wrote: Hi, Nathan Letwory wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Indeed, but it happens regularly that builds break on different platforms, and even more so because developers *don't build with all features enabled* (while in theory they should always verify the entire build before doing any commits). Sure, triggering manually is a way, but it is even better to not have to do that. Developers are lazy beings (hence they are developers). With the amount of developers that we have commiting I think its especially nice if our buildslaves would just build the moment they don't have anything to do and are notified of changes. Well, just triggering isn't enough. It wouldn't make developers check buildbot logs, IMO. It should also punish developers who breaks something. Or at least notify them. Agreed. /Nathan - -- Nathan Letwory Letwory Interactive | Studio Lumikuu http://www.letworyinteractive.com | http://www.lumikuu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObeXKAAoJEKtfN7KsE0TtjwwH/3FSUwYBqxciBlBZKWkWO8cY JD88NsNH8MWCrNGoFkBEYg5CMjcRaTTctHICUVavjNA8xpfocbwtpiI7yPg57THx yj0mTBtyfgifR/ANGAUdAHM0rmigtO4i4KrLPdIu/YTpBurEpO3qXXi8r/PJanDl 9xDotbo6RmP/TUTwZDOKL/Fvmm9QccX2kXzInHZwNmtIJ2n+y2AURIJfQ/t/mj7f MK7WMeXlAngY3XRM5qT43NRmC7JYPsu8SobWWIHrAQ7dYuPcbCOBo9Xj6HUq8E3S 0C7bVAyqi7D8qs8oOuMKRjFGk5afxOaTjFbgh2xvLAzjdbdmP2Y2SEvqwcaP95c= =WxLy -END PGP SIGNATURE- ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
