harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [testing] HARMONY-995: adding new target to builds for automatic testing
Date Tue, 26 Sep 2006 12:36:49 GMT

On Sep 26, 2006, at 2:49 AM, Vladimir Ivanov wrote:

> On 9/26/06, Geir Magnusson Jr. <geir@pobox.com> wrote:
>>
>>
>> On Sep 25, 2006, at 6:49 AM, Vladimir Ivanov wrote:
>>
>> > On 9/25/06, Geir Magnusson Jr. < geir@pobox.com> wrote:
>> >>
>> >>
>> >> On Sep 25, 2006, at 5:05 AM, Vladimir Ivanov wrote:
>> >>
>> > Actually, now 3 targets should be called one-by-one (4 in case of
>> > vm) to
>> > reproduce development cycle.
>> > Of cause, "external tool" can do it but it is seems more reasonable
>> > to have
>> > this command in the build.
>>
>> I see what you mean.  I don't agree.  The nice thing about having the
>> external tool, is that the external tool can report on which phase
>> broke.  By calling an "ubertarget" that does everything, all it knows
>> is that the ubertarget failed.
>>
>> For example, if you know that the tests failed, the system could
>> examine the svn log between the time that the tests passed, and the
>> time they failed, and send a note to developers giving them a hint of
>> what changed to help find out what went wrong.
>>
>> If sophisticated enough, it could just figure it out from stack
>> trace, and mail the responsible developer directly :)
>
>
>
> In the case when we have one target the building strategy defined  
> by build.
> It just do step-by-step and report failure if any step failed (and  
> stop to
> wait fix). So we have one 'event' for one module - "ws updated" and  
> after it
> we should test these changes (that includes update, build and  
> test). If any
> phase failed no need to do other.

Right, but the system can easily automate doing the three steps in  
phases.  The "build-test infrastructure" does that already.  Well get  
timing info too...

>
> It works for each project while project and tests placed in the one  
> ws.
>
> The external tool may implement some build sequences but seems it  
> should be
> defined be build itself.

It is defined by build, but people are given the freedom of  
individual piece-parts for good reason.

geir

>
>
>
> thanks, Vladimir
>
>
>
>>
>> > Issue http://issues.apache.org/jira/browse/HARMONY-1565 with
>> > trivial update
>> > was created.
>>
>> So do we really need this?
>>
>> geir
>>
>>
>> >
>> > thanks, Vladimir
>> >
>> >
>> >
>> > geir
>> >>
>> >> >
>> >> >
>> >> >
>> >> > Thanks, Vladimir
>> >> >
>> >> >
>> >> >
>> >> > ---------- Forwarded message ----------
>> >> > From: Vladimir Ivanov (JIRA) <jira@apache.org>
>> >> > Date: Sep 25, 2006 3:31 PM
>> >> > Subject: [jira] Updated: (HARMONY-995) [testing] add support of
>> >> proxy
>> >> > settings for get-task
>> >> > To: ivavladimir@gmail.com
>> >> >
>> >> >    [ http://issues.apache.org/jira/browse/HARMONY-995?page=all ]
>> >> >
>> >> > Vladimir Ivanov updated HARMONY-995:
>> >> > ------------------------------------
>> >> >
>> >> >   Attachment: build.patch
>> >> >
>> >> > add notification, timeouts etc
>> >> >
>> >> >> [testing] add support of proxy settings for get-task
>> >> >> ----------------------------------------------------
>> >> >>
>> >> >>                 Key: HARMONY-995
>> >> >>                 URL: http://issues.apache.org/jira/browse/
>> >> HARMONY-995
>> >> >>             Project: Harmony
>> >> >>          Issue Type: Bug
>> >> >>          Components: build - test - ci
>> >> >>            Reporter: Vladimir Ivanov
>> >> >>            Priority: Minor
>> >> >>         Attachments: build.patch, build.xml.patch,  
>> build.xml.patch
>> >> >>
>> >> >>
>> >> >> 1) add external property file with proxy settings to use it int
>> >> the
>> >> > build.xml for <get> task (when needed).
>> >> >> 2) add '/c' symbol to run CC on win
>> >> >> 3) seems, that readme.txt file should be updated to point as
>> >> >> define proxy
>> >> > for svn and get certificate
>> >> >
>> >> > --
>> >> > This message is automatically generated by JIRA.
>> >> > -
>> >> > If you think it was sent incorrectly contact one of the
>> >> > administrators:
>> >> > http://issues.apache.org/jira/secure/Administrators.jspa
>> >> > -
>> >> > For more information on JIRA, see: http://www.atlassian.com/
>> >> > software/jira
>> >>
>> >>
>> >>  
>> ---------------------------------------------------------------------
>> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> >> To unsubscribe, e-mail: harmony-dev- 
>> unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: harmony-dev-
>> >> help@incubator.apache.org
>> >>
>> >>
>>
>>
>> ---------------------------------------------------------------------
>> Terms of use : http://incubator.apache.org/harmony/mailing.html
>> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: harmony-dev- 
>> help@incubator.apache.org
>>
>>


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message