Re: Building backwards in time

How does labeling solve any problems? We don't want to stop people from
committing during builds as there can be several going concurrently and even
the quickest take a long time. We also don't want to build every single
commit as most of the time the tests will pass. It makes sense to
continuously build at the fastest interval that your resources allow,
backtracking only when a failure is encountered.

On Tue, Mar 24, 2009 at 5:08 PM, Doug Farmer <[email protected]> wrote:

> If you label your builds first and check out the code from that label you
> will not run into the issue with someone checking in changes to the
> repository while a build is occurring.
>
> Thanks,
> Doug Farmer
>
>
>
> On Tue, Mar 24, 2009 at 4:44 PM, 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.
>>
>>
>> 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
>>
>>
>
>
> ------------------------------------------------------------------------------
> 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