On Thu, Aug 15, 2013 at 2:24 PM, <dlellis_at_rockwellcollins.com> wrote:
>> >> With more complexity comes more bugs and process missteps. We're
>> >> really
>> > striving to keep things as simple as possible. We're fundamentally
>> > accepting of update times going from 2 seconds to 2 minutes. Its harder
>> > when 2 minutes becomes 20 minutes.
>> Are your build systems on the other side of the world from the
>> repository? The quick fix might be to reduce the latency one way or
>> another (move one of the pieces, use the wandisco distributed repo
>> approach, etc?) or automate with something like jenkins so you don't
>> have a person waiting.
> Yes, and that's a big contributor. Co-location helps significantly, but
> isn't an option in our case. I'll take a look at your suggestions.
Depending on your platform and tools, there are times when it works
better to have a remote display to a machine on a network where the
real work happens than to copy everything locally. And if you can
automate with Jenkins, you don't really even need the display for the
build, although you do have to somehow commit your changes to
Received on 2013-08-15 21:38:25 CEST