[Bf-committers] Official Automated Builds

[pete larabell]

I can do automated builds for FreeBSD 8.2-RELEASE i386, and soon
amd64. As of Friday python32 for BSD/amd64 was still a link to
python31, but BSD/i386 has proper python32.

I can also have a system in place to detect build failures.

If BF does go the VirtualBox route (which I'd prefer since that what I
use for many machines already) I can make both i386 and amd64 FreeBSD
virtuals, and I can maintain them.

Will be looking tomorrow for a way to get amd64 builds working again.

As a side note:

I currently have my own little automated build system in place for
ubuntu 10.10 x86_32 and x86_64 and FreeBSD 8.2-RELEASE i386 and
(broken due to aforementioned python32) amd64. A cron job on each VBox
runs an svn up, does needed cmake-ing, and make-ing + make
install-ing. I don't currently have the "build failed" detection
system built, but I could write something in Perl that'd check that
pretty easily. (or is using Perl frowned on by many python people
here? xD )

Cheers
Peter

On Sun, Mar 13, 2011 at 9:22 PM, Brecht Van Lommel
<brechtvanlommel at pandora.be> wrote:

    Hi,

    First let me say, doing the whole continuous integration web service
    thing is not what I signed up for. It's valuable, but someone else
    will have to volunteer for that.

    Mainly my motivation is getting good reference builds for bug
    reporting, and finding and solving build and installation issues for
    releases sooner so we can do more efficient releases. So the intention
    for these builds would be to be identical to release builds.

    Brecht.
    _______________________________________________
    Bf-committers mailing list
    Bf-committers at blender.org
    http://lists.blender.org/mailman/listinfo/bf-committers




On Sun, Mar 13, 2011 at 9:22 PM, Brecht Van Lommel
<brechtvanlommel at pandora.be> wrote:
>
> Hi,
>
> First let me say, doing the whole continuous integration web service
> thing is not what I signed up for. It's valuable, but someone else
> will have to volunteer for that.
>
> Mainly my motivation is getting good reference builds for bug
> reporting, and finding and solving build and installation issues for
> releases sooner so we can do more efficient releases. So the intention
> for these builds would be to be identical to release builds.
>
> Brecht.
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers