RE: Nightly Build Reports Too Big (again)
Robert Burrell Donkin wrote: > i could reduce the quantity of warnings etc > but perhaps they are useful reminders. Perhaps. > what i could do is add a 'quiet' property which would allow people to > decide whether they need to see all that noise or not. opinions? If that just means that the nightly builds run quiet, that'd fine with me. As Stefano notes, we're currently working around it for the nightly build using grep. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
Robert Burrell Donkin ha scritto: > On 9/9/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: >> On 8/19/07, Norman Maurer <[EMAIL PROTECTED]> wrote: Any idea how we can eliminate some of this extraneous garbage so that the build report can be posted? Or should I just shut down the nightly builds because no one cares anyway? --- Noel >>> Sorry I'm no ant guru. Maybe robert can help ? >> i hope to be able to take a look sometime this week > > i've taken a quite look. i could reduce the quantity of warnings etc > but perhaps they are useful reminders. > > what i could do is add a 'quiet' property which would allow people to > decide whether they need to see all that noise or not. opinions? > > - robert I have no preferences. I think the main issue was the message size limit in the mailing list and the grep solved it. "make it quiet" or grepping does not make so much difference. Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
On 9/9/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > On 8/19/07, Norman Maurer <[EMAIL PROTECTED]> wrote: > > > Any idea how we can eliminate some of this extraneous garbage so > > > that the build report can be posted? Or should I just shut down the > > > nightly > > > builds because no one cares anyway? > > > > > > --- Noel > > > > Sorry I'm no ant guru. Maybe robert can help ? > > i hope to be able to take a look sometime this week i've taken a quite look. i could reduce the quantity of warnings etc but perhaps they are useful reminders. what i could do is add a 'quiet' property which would allow people to decide whether they need to see all that noise or not. opinions? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
On 8/19/07, Norman Maurer <[EMAIL PROTECTED]> wrote: > Noel J. Bergman schrieb: > > Something has been changed in the past couple of weeks, and the nightly > > build e-mails are broken again. Since the last one, containing 94K, was > > sent on August 10th, we have not only gone over 100K of output, we're at > > 239K of output! i suspect that it's a combination of the more comprehensive javadocs and the integration tests for IMAP i ported > > As a point of reference, back in December, the breakdown was: > > > > > >> Deprecation messages for main compile: ~20K > >> Deprecation messages for junit compile: ~12K > >> JUnit output: ~20K > >> xdocs output: ~ 6K > >> JavaDoc messages: ~30K > >> > >> ~88K > >> > > > > We then worked to eliminate all of the Deprecation messages, and had plenty > > of room for additional unit test output. Now we have: > > > > [javadoc] Loading source file [...]: ~143K > > [javadoc] Misc javadoc messages ~ 29K > > [copy] Copying files to : ~ 9K > > [mkdir] Created dir: : ~ 9K > > > > messages. Any idea how we can eliminate some of this extraneous garbage so > > that the build report can be posted? Or should I just shut down the nightly > > builds because no one cares anyway? > > > > --- Noel > > > > > > Sorry I'm no ant guru. Maybe robert can help ? i hope to be able to take a look sometime this week - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
Noel J. Bergman ha scritto: > Noel J. Bergman wrote: >> Stefano Bagnara wrote: >>> What about a "| grep -v javadoc" while you write the mail body? >> Sure, I'll give it a shot and we'll see. > > Please review the latest nightly build report. We're just under 64K. > Satisfied with the content? Anything else we want to strip out? > > --- Noel At the moment it is ok!. If we'll have the size problem again we can move to an inclusive filter: in fact the most important rows contains (case insensitive) SUCCESS/FAIL e.g: grep -i "\(success\|fail\)" But this would be a bit extreme (and cryptic). Thank you, Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nightly Build Reports Too Big (again)
Noel J. Bergman wrote: > Stefano Bagnara wrote: > > What about a "| grep -v javadoc" while you write the mail body? > Sure, I'll give it a shot and we'll see. Please review the latest nightly build report. We're just under 64K. Satisfied with the content? Anything else we want to strip out? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nightly Build Reports Too Big (again)
Stefano Bagnara wrote: > What about a "| grep -v javadoc" while you write the mail body? Sure, I'll give it a shot and we'll see. > I would like to have nightly for everyone of our projects: some day ago > I had to do a nightly build for jspf to let an user test a bugfix. > Where do you run this nighly builds? ASF hardware or external resources? I run them on my infrastructure, on my side of several firewalls. I'd be happy to add additional JAMES projects to the build. You've seen the script. Just give me some idea of what else you want added. > You just wrote on general@ that ASF is planning allowing other java > based tools in the future: what about continuum? A continuum instance > with all of our projects would be great. Continuum is already running, but still exhibiting issues. Not making our infra team happy, and getting worse as more things go into it. As noted above, I'm perfectly happy to do the builds. I have pretty much dedicated a fast Athlon ubuntu system to it, at least during build hours. :-) --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
Noel J. Bergman ha scritto: > We block those attachments, IIRC. :-) Besides, the full script is: > > #!/bin/sh > # > # > ( >echo "To: JAMES Server Development " >echo "From: JAMES Nightly Build System <[EMAIL PROTECTED]>" >echo "Subject: JAMES Server Nightly Build Report" >echo > >export JAVA_HOME=/usr/local/java >PATH=$PATH:$HOME/bin >export PATH >cd ~/ASF/james/server/trunk >rm -rf dist/* >echo >echo Updating From Source Control >echo >svn revert -R . >svn up >echo >echo Do a Clean Build with Unit Tests and Distribution Packages >echo >ant -Ddeprecation=off dist >echo >echo Done. Packages Will Be Uploaded To The Nightly Repository. >echo > ) 2>&1 | /home/noel/ASF/sendmail.py -f [EMAIL PROTECTED] -t I would go for the easy fix and change the last line with this one: ) 2>&1 | grep -v javadoc | /home/noel/ASF/sendmail.py -f [EMAIL PROTECTED] -t Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
Noel J. Bergman ha scritto: > Something has been changed in the past couple of weeks, and the nightly > build e-mails are broken again. Since the last one, containing 94K, was > sent on August 10th, we have not only gone over 100K of output, we're at > 239K of output! > > As a point of reference, back in December, the breakdown was: > >> Deprecation messages for main compile: ~20K >> Deprecation messages for junit compile: ~12K >> JUnit output: ~20K >> xdocs output: ~ 6K >> JavaDoc messages: ~30K >> >> ~88K > > We then worked to eliminate all of the Deprecation messages, and had plenty > of room for additional unit test output. Now we have: > > [javadoc] Loading source file [...]: ~143K > [javadoc] Misc javadoc messages ~ 29K > [copy] Copying files to : ~ 9K > [mkdir] Created dir: : ~ 9K > > messages. Any idea how we can eliminate some of this extraneous garbage so > that the build report can be posted? Or should I just shut down the nightly > builds because no one cares anyway? > > --- Noel What about a "| grep -v javadoc" while you write the mail body? I think it is useful anyway to keep them even if we are not able to fix email notifications. (e.g: I monitor the target folder once a day) The build is also useful for users experiencing some bug with 2.3.1 and wanting to help us testing trunk to tell us if it is reproducible with it. I would like to have nightly for everyone of our projects: some day ago I had to do a nightly build for jspf to let an user test a bugfix. Where do you run this nighly builds? ASF hardware or external resources? You just wrote on general@ that ASF is planning allowing other java based tools in the future: what about continuum? A continuum instance with all of our projects would be great. I'm not a member, but I could help configuring our instance if help is needed. Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
> If you make a tail -20 of log (and full log... pkzip & attach as file?) :-) We block those attachments, IIRC. :-) Besides, the full script is: #!/bin/sh # # ( echo "To: JAMES Server Development " echo "From: JAMES Nightly Build System <[EMAIL PROTECTED]>" echo "Subject: JAMES Server Nightly Build Report" echo export JAVA_HOME=/usr/local/java PATH=$PATH:$HOME/bin export PATH cd ~/ASF/james/server/trunk rm -rf dist/* echo echo Updating From Source Control echo svn revert -R . svn up echo echo Do a Clean Build with Unit Tests and Distribution Packages echo ant -Ddeprecation=off dist echo echo Done. Packages Will Be Uploaded To The Nightly Repository. echo ) 2>&1 | /home/noel/ASF/sendmail.py -f [EMAIL PROTECTED] -t if [ -d ~/ASF/james/server/trunk/dist/*/downloads ]; then cd ~/ASF/james/server/trunk/dist/*/downloads rsync -rlpvz --delete --exclude HEADER.html -e ssh . people.apache.org:/www/people.apache.org/builds/james/nightly/ fi exit 0 So to do what you suggest would require changing the nightly build script along the lines of http://lists.freebsd.org/pipermail/freebsd-questions/2005-April/083518.html or http://fedora-tn.org/?q=node/72. An alternative would be to enhance our sendmail script to support the attachment commands found in mutt and metamail (q.v. http://www.shelldorado.com/articles/mailattachments.html). Anyone up to do that work? If so, please remember to change the message subject when replying. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
Noel J. Bergman schrieb: Something has been changed in the past couple of weeks, and the nightly build e-mails are broken again. Since the last one, containing 94K, was sent on August 10th, we have not only gone over 100K of output, we're at 239K of output! As a point of reference, back in December, the breakdown was: Deprecation messages for main compile: ~20K Deprecation messages for junit compile: ~12K JUnit output: ~20K xdocs output: ~ 6K JavaDoc messages: ~30K ~88K We then worked to eliminate all of the Deprecation messages, and had plenty of room for additional unit test output. Now we have: [javadoc] Loading source file [...]: ~143K [javadoc] Misc javadoc messages ~ 29K [copy] Copying files to : ~ 9K [mkdir] Created dir: : ~ 9K messages. Any idea how we can eliminate some of this extraneous garbage so that the build report can be posted? Or should I just shut down the nightly builds because no one cares anyway? --- Noel Sorry I'm no ant guru. Maybe robert can help ? bye Norman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly Build Reports Too Big (again)
Hi Noel, If you make a tail -20 of log (and full log... pkzip & attach as file?) :-) Saludos, Guillermo - Original Message - From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Developers List" Sent: Sunday, August 19, 2007 12:00 AM Subject: Nightly Build Reports Too Big (again) Something has been changed in the past couple of weeks, and the nightly build e-mails are broken again. Since the last one, containing 94K, was sent on August 10th, we have not only gone over 100K of output, we're at 239K of output! As a point of reference, back in December, the breakdown was: Deprecation messages for main compile: ~20K Deprecation messages for junit compile: ~12K JUnit output: ~20K xdocs output: ~ 6K JavaDoc messages: ~30K ~88K We then worked to eliminate all of the Deprecation messages, and had plenty of room for additional unit test output. Now we have: [javadoc] Loading source file [...]: ~143K [javadoc] Misc javadoc messages ~ 29K [copy] Copying files to : ~ 9K [mkdir] Created dir: : ~ 9K messages. Any idea how we can eliminate some of this extraneous garbage so that the build report can be posted? Or should I just shut down the nightly builds because no one cares anyway? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Nightly Build Reports Too Big (again)
Something has been changed in the past couple of weeks, and the nightly build e-mails are broken again. Since the last one, containing 94K, was sent on August 10th, we have not only gone over 100K of output, we're at 239K of output! As a point of reference, back in December, the breakdown was: > Deprecation messages for main compile: ~20K > Deprecation messages for junit compile: ~12K > JUnit output: ~20K > xdocs output: ~ 6K > JavaDoc messages: ~30K > > ~88K We then worked to eliminate all of the Deprecation messages, and had plenty of room for additional unit test output. Now we have: [javadoc] Loading source file [...]: ~143K [javadoc] Misc javadoc messages ~ 29K [copy] Copying files to : ~ 9K [mkdir] Created dir: : ~ 9K messages. Any idea how we can eliminate some of this extraneous garbage so that the build report can be posted? Or should I just shut down the nightly builds because no one cares anyway? --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
