Re: Building backwards in time

Hi!

On Tue, Mar 24, 2009 at 21:44, Uri Moszkowicz <[email protected]> wrote:
> You are assuming that all testing can be completed in such a short period of
> time that multiple commits cannot possibly sneak in between tests, which
> isn't always the case. The CC tool seems to be designed at least in part for
> non-trivial testing as it supports distributed builds and time limits up to
> a week in length.

If you has builds that take a week to complete, then I would say that
you need to address that issue and do whatever it takes to break up
your build process in more steps. Each step should finish as fast as
possible. I would consider having a set if builds that depend on the
previous step and create in a sense a pipeline in which a result is
promoted after each successful step. It is as you probably will agree
upon essential that the developers that break a build get feedback as
fast as possible. For the easy parts this implies minutes rather then
anything else. If a late step in for example a integration step fails,
this should end the build and the result should be reported back and
most likely be considered an open bug that has the highest priority
since it prevents the project/product to be in a state where you can
put it into production.

So, in my opinion there isn't a need for back tracking builds. It
would be a very complicated way to solve the wrong problem.

/Thomas


> On Tue, Mar 24, 2009 at 4:30 PM, Thomas Sundberg
> <[email protected]> wrote:
>>
>> Hi!
>>
>> If I understand you correct, you would want to use CC to step
>> backwards, check in by check in until you can isolate a specific check
>> in that broke the build?
>>
>> I really can't see the use for such a function since a normal build
>> cycle is that you use CC to build as soon as something has been
>> checked in, you will therefore have a record of successful builds and
>> all of a sudden a failed build. It is trivial to find the check in
>> that broke the build in this scenario so there is no need to be able
>> to step backwards. If the norm is that the build fails every time,
>> then you have another problem that you need to deal with.
>>
>> /Thomas
>>
>> On Tue, Mar 24, 2009 at 20:36, Uri Moszkowicz <[email protected]> wrote:
>> > Hi,
>> > I'd just like to suggest a feature for CC. It would be nice to be able
>> > to
>> > build projects using historical checkouts. This would be useful when
>> > there
>> > is a failure and you are trying to isolate the exact commit that caused
>> > the
>> > problem. CC could accept a range of builds to explore or would accept a
>> > specific date. I'm guessing that this has come up before but I don't see
>> > how
>> > I can search mailing lists on SF anymore. What do you all think?
>> >
>> > Thanks,
>> > Uri
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
>> > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
>> > easily build your RIAs with Flex Builder, the Eclipse(TM)based
>> > development
>> > software that enables intelligent coding and step-through debugging.
>> > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> > _______________________________________________
>> > Cruisecontrol-user mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>> >
>> >
>>
>>
>>
>> --
>> -------------------------------------------------------
>> Thomas Sundberg
>> M. Sc. in Computer Science
>>
>> Agical AB
>> Västerlånggatan 79, 2 tr
>> 111 29 Stockholm, SWEDEN
>>
>> Mobile: +46 70 767 33 15
>> E-mail: [email protected]
>> http://www.agical.com
>>
>>
>> ------------------------------------------------------------------------------
>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
>> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
>> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
>> software that enables intelligent coding and step-through debugging.
>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> _______________________________________________
>> Cruisecontrol-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Cruisecontrol-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>
>



-- 
-------------------------------------------------------
Thomas Sundberg
M. Sc. in Computer Science

Agical AB
Västerlånggatan 79, 2 tr
111 29 Stockholm, SWEDEN

Mobile: +46 70 767 33 15
E-mail: [email protected]
http://www.agical.com

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com