Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 98772 invoked from network); 27 Sep 2006 11:22:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Sep 2006 11:22:39 -0000 Received: (qmail 83906 invoked by uid 500); 27 Sep 2006 11:22:36 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 83852 invoked by uid 500); 27 Sep 2006 11:22:36 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 83799 invoked by uid 99); 27 Sep 2006 11:22:35 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Sep 2006 04:22:35 -0700 Authentication-Results: idunn.apache.osuosl.org smtp.mail=geir@pobox.com; spf=unknown X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received-SPF: unknown (idunn.apache.osuosl.org: domain pobox.com does not designate 216.86.168.179 as permitted sender) Received: from [216.86.168.179] ([216.86.168.179:1415] helo=mxout-04.mxes.net) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id A0/D1-24938-FEE5A154 for ; Wed, 27 Sep 2006 04:22:28 -0700 Received: from [10.1.190.106] (unknown [72.254.46.9]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 5B353A3202 for ; Wed, 27 Sep 2006 07:22:20 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <7273946b0609262152q2dc53798o45b9f2488bac17a4@mail.gmail.com> References: <7273946b0609250205n1526db31v609522ca3e13e194@mail.gmail.com> <7273946b0609250349s3298c40aq57797d47c88cbdce@mail.gmail.com> <868C5E82-4777-4749-A12B-2456EFC60AF5@pobox.com> <7273946b0609252349he30fcccndb300b7578baf9d7@mail.gmail.com> <7E0C6990-A34B-4A4D-816D-0A3EFC5AF485@pobox.com> <7273946b0609261947y6b6abcf3h11e2ad36259a62d@mail.gmail.com> <30B5B1F0-038A-496F-9E66-5A4A5C27B4A7@pobox.com> <7273946b0609262152q2dc53798o45b9f2488bac17a4@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1E4B3BDC-CB6A-4A05-A782-8C80E0CE92AF@pobox.com> Content-Transfer-Encoding: 7bit From: "Geir Magnusson Jr." Subject: Re: [testing] HARMONY-995: adding new target to builds for automatic testing Date: Wed, 27 Sep 2006 07:22:21 -0400 To: harmony-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.2) X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Sep 27, 2006, at 12:52 AM, Vladimir Ivanov wrote: > On 9/27/06, Geir Magnusson Jr. wrote: >> >> >> On Sep 26, 2006, at 10:47 PM, Vladimir Ivanov wrote: >> >> > On 9/26/06, Geir Magnusson Jr. wrote: >> >> >> >> <...> >> >> >> >> 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... >> > >> > >> > Yes, but some people want to receive one notification for one >> > module (like >> > 'classlib OK' that means ws was built and all tests passed). In the >> > current >> > model this feature is not accessible. >> >> Why not? If someone wanted that, I'd design it so no mail is send on >> success of fetch and build, but only on tests. > > > > In this case he will miss the 'build-broken' event. We seem to be having a bit of a communication issue. No, he wouldn't miss it, because the system would send mail in that case. The system would send mail in case of failure for every case, and only success for the tests, as you seemed to be asking. Actually, my configuration wouldn't send mail for anything except "transition" - first failure, and then first recovery... > >> >> > <...> >> >> >> >> > 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. >> > >> > >> > Nobody takes away the freedom. >> > My suggestion was to add flexibility: if somebody wants build >> and test >> > Harmony by one command he can easily do it (not now). If other >> > peoples want >> > to do it step-by-step it is OK. It is their choice. >> > But build should provide both capabilities (at least, while it >> > costs nothing >> > - 1 line of code). >> >> Agreed - but who wants that now? IOW, what are you doing that >> requires this? > > > > Sometimes I checkout ws as clean and for me it will be convenient to > fetch-depend, build and test it at one moment. Of cause, it is not > too often > :) > > > >> > >> > By the way, the "build-test infrastructure" may be updated to >> > support both >> > modes by switch: do all commands step-by-step or run one command. >> >> I guess I still don't understand why, since I don't see to the user >> what the difference is if the system does three actions, or just one. > > > For CC, the difference is three or one notification if user does > not want to > miss some events. But you can send just one email with a summary of everything that happened during that run. The fact that the system did : call fetch-depends call build clean call build call test should have no bearing on how many emails it sends. geir > > thanks, Vladimir > > geir >> >> >> > thanks, Vladimir >> > >> > 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) >> >> >> >> > 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 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 >> >> >> >> >> >> >> --------------------------------------------------------------------- >> 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