There's never been a guarantee that the development sources compile for
everybody at all moments. That's why they are development sources. I
appreciate the Hudson process and quite often the change to get things
compiling on a given platform are obvious, but sometimes they aren't and one
needs to rely on the help of those who know the other platforms better. I
don't see why they would have get their own copy of the offending source
code from anywhere other than the "next" branch.
Tim
On Sat, Nov 13, 2010 at 5:57 PM, Alex Perry <alex.pe...@ieee.org> wrote:
> On Sat, Nov 13, 2010 at 7:35 AM, Arnt Karlsen <a...@c2i.net> wrote:
> > On Sat, 13 Nov 2010 09:57:14 +0000, James wrote in message
> >> On 12 Nov 2010, at 23:44, Curtis Olson wrote:
> >> > My personal rule-of-thumb is to only commit when I've got time to
> >> > watch the Hudson board go green - it's on an hourly poll at the
> >> > moment, though we can allow other users to manually kick off
> >> > builds, if you ask Gene nicely.
> >>
> >> Ah, sorry to disappoint, but you have to commit to Git first - unlike
> >> some setups, we haven't engineered a 'compile before publish' system.
> >> Hence my ensuring I have time to watch Hudson *after* a commit, and,
> >> for example, make a fix commit if I broke something.
> >
> > ..an idea; a bad commit that doesn't compile successfully,
> > can it be reverted automatically? That way git would stay
> > unbroken, until new unbroken code is added etc and compiles
> > successfully.
>
> I like automatic build systems which, if ..
> * a commit fails to build for any platform,
> * the prior build passed for every platform,
> * only one commit happened in that time,
> * the word "CRITICAL" is nowhere in the change description,
> ... automatically rolls back ... and tells someone.
>
> As a bonus, if it fails at the third bullet, it can automatically
> submit builds for all the intervening releases in an attempt to make
> the bullet pass.
>
> As another bonus, after the rollback, the fifth bullet looks back at
> the first bullet to see whether it failed to build for every platform
> and, if so, it would be nice for someone to be notified.
>
>
> ------------------------------------------------------------------------------
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
