Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 27523 invoked from network); 4 Mar 2003 21:39:02 -0000 Received: from unknown (HELO mail1.FutureTrade.com) (66.237.1.75) by daedalus.apache.org with SMTP; 4 Mar 2003 21:39:02 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Emailing Build results Date: Tue, 4 Mar 2003 13:39:08 -0800 Message-ID: <69C78A93CD5E934A84F2B90747D91CCF6D98E7@mail1.FutureTrade.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Emailing Build results Thread-Index: AcLieDA/HBffvaxWRzm+kLsUWIkj7gAF8uUgAABpnZAAAFdJcAAAWwXQAAA+q2AAACnZAA== From: "Alexei Betin" To: "Ant Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N well, in fact I'd need rather something like: > -----Original Message----- > From: Alexei Betin=20 > Sent: Tuesday, March 04, 2003 1:35 PM > To: Ant Users List > Subject: RE: Emailing Build results >=20 >=20 > Aha, I am getting closer... >=20 > failing task does terminate the build, but > by using the structure like below I seem to be getting=20 > what I want: >=20 > > > > >=20 > Thanks for all help! >=20 > ~Alexei >=20 > > -----Original Message----- > > From: Chris Reeves [mailto:CReeves@medfusion.net] > > Sent: Tuesday, March 04, 2003 1:26 PM > > To: Ant Users List > > Subject: RE: Emailing Build results > >=20 > >=20 > > Probably so. Like I said, it's been working for months, so=20 > > I'm gonna let > > it be. > >=20 > > However, I'd like to hear if you experiment with it. > >=20 > > Thanks, > > Chris > >=20 > > > -----Original Message----- > > > From: Alexei Betin [mailto:ABetin@futuretrade.com]=20 > > > Sent: Tuesday, March 04, 2003 4:16 PM > > > To: Ant Users List > > > Subject: RE: Emailing Build results > > >=20 > > >=20 > > > I like this approach except for using , > > > I wonder if there is a way to do it using instead? > > >=20 > > > Thanks, > > > ~Alexei > > >=20 > > >=20 > > > > -----Original Message----- > > > > From: Chris Reeves [mailto:CReeves@medfusion.net] > > > > Sent: Tuesday, March 04, 2003 1:10 PM > > > > To: Ant Users List > > > > Subject: RE: Emailing Build results > > > >=20 > > > >=20 > > > > I use a slightly different approach to have the buld=20 > results sent. > > > >=20 > > > > First, I created a second, separate ant build script that=20 > > wraps my=20 > > > > build.xml file. > > > >=20 > > > > This second script checks the project out of cvs, then=20 > > executes the=20 > > > > build.xml present at the root of the project. When the ant call=20 > > > > completes, the log file is attached to a mail message.=20 > > This occurs=20 > > > > even if the wrapped build fails. > > > >=20 > > > > I'm sure there's a cleaner way to do this, but it has run=20 > > > for months=20 > > > > with no problems. > > > >=20 > > > > Additionally, it's great to see the "Failed" or=20 > > "Succeeded" on the=20 > > > > subject line, so I don't have to open each message and=20 > > > scour the logs=20 > > > > just to discover the build succeeded. > > > >=20 > > > > Chris > > > >=20 > > > >=20 > > > > ... > > > >=20 > > > > > > > >=20 > > > >=20 > > > > > > > > > > > > > > > >=20 > > > > > > > cvs_checkout"> > > > >=20 > > > > > > > ${project.root.dir}/${project.antfile}"/> > > > >=20 > > > > > > > executable =3D=20 > "/usr/java/ant/bin/ant" > > > > output =3D > > > > "${log.dir}/nightly_build_results_${filename.suffix}.txt" > > > > resultproperty =3D = "project.build.result" > > > > outputproperty =3D=20 > "project.build.output"> > > > > "${project.anttarget}"/> > > > > > > > >=20 > > > > > > > >=20 > > > > > > > >=20 > > > >=20 > > > > > > > > > > > > > > > >=20 > > > > > > > build_project"> > > > >=20 > > > > > > value=3D"Failed!!!"> > > > > > > > arg2=3D"${project.build.result}"/> > > > > > > > >=20 > > > > > > > value=3D"Succeeded!!!"> > > > > > > > arg2=3D"${project.build.result}"/> > > > > > > > >=20 > > > > "${to.address}" > > > > from =3D=20 > > "${from.address}" > > > > subject =3D=20 > "${build.result} > > > > ${project.longname} Nightly Build - ${build.time}" > > > > mailhost =3D=20 > "${smtp.server}" > > > > messagefile =3D > > > > "${log.dir}/nightly_build_results_${filename.suffix}.txt"> > > > > > > > >=20 > > > > > > > >=20 > > > > > > > >=20 > > > > ... > > > >=20 > > > > > -----Original Message----- > > > > > From: Alexei Betin [mailto:ABetin@futuretrade.com] > > > > > Sent: Tuesday, March 04, 2003 4:01 PM > > > > > To: Ant Users List > > > > > Subject: Emailing Build results > > > > >=20 > > > > >=20 > > > > > what are reasonable options for emailing nightly=20 > Build results? > > > > >=20 > > > > > MailLogger seems to have no way to attach the build log > > > > > or use properties in Subject, > > > > >=20 > > > > > also I am already using NoBannerLogger - which leaves no > > > > > place for MailLogger... > > > > >=20 > > > > > task cannot help me, because if I put it at the=20 > > end of my=20 > > > > > build script, and the build fails, it'll never get to=20 > > execute it. > > > > >=20 > > > > > Is there a way to ensure a task is always called at the end? > > > > > maybe using different build files with or ?=20 > > > > > would not help me here because it can only wrap=20 > > > > > tasks and not targets... > > > > >=20 > > > > > Finally, I understand I can write my own Logger, > > > > > but for a couple of reasons I don't want to - I would=20 > > > rather prefer=20 > > > > > to get the job done by some batch file, but I wonder if I=20 > > > am missing=20 > > > > > a nice pure-Ant solution > > > > >=20 > > > > > Thanks, > > > > > ~Alexei > > > > >=20 > > > > >=20 > > > >=20 > > >=20 > >=20 > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > > > > > For additional commands, e-mail: user-help@ant.apache.org > > > > >=20 > > > > >=20 > > > >=20 > > > >=20 > > >=20 > >=20 > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > > > > For additional commands, e-mail: user-help@ant.apache.org > > > >=20 > > > >=20 > > >=20 > > >=20 > >=20 > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > > > For additional commands, e-mail: user-help@ant.apache.org > > >=20 > > >=20 > >=20 > >=20 > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > > For additional commands, e-mail: user-help@ant.apache.org > >=20 > >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org > For additional commands, e-mail: user-help@ant.apache.org >=20 >=20