On Sat, 13 Nov 2010 09:57:14 +0000, James wrote in message 
<0275fe52-84ce-4e88-a29c-b1382f3ae...@mac.com>:

> 
> 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.
> > 
> > How do you get a change over to hudson before committing it to
> > git?  (maybe a dumb question?)
> 
> 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.


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

------------------------------------------------------------------------------
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

Reply via email to