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
snip
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
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
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
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
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
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 server-dev@james.apache.org
echo From: JAMES Nightly Build System [EMAIL PROTECTED]
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
Noel J. Bergman ha scritto:
We block those attachments, IIRC. :-) Besides, the full script is:
#!/bin/sh
#
#
(
echo To: JAMES Server Development server-dev@james.apache.org
echo From: JAMES Nightly Build System [EMAIL PROTECTED]
echo Subject: JAMES Server Nightly Build
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
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 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
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:
13 matches
Mail list logo
