Community
Participate
Working Groups
In the past, when a cronjob would start our "bootstrap" build file, I set it up so all output was "tee'd" to another local file in addition to the logs put in "buildlogs". This was handy to have one big log to search through for certain types of errors. But, the file is several hundred megabytes large, and now, running on Hudson, it all goes to the Hudson console. I am pretty sure Hudson (and people's browsers!) will not handle that much data well. So, this bug is to remove that redirection. If anything, we should "write to console" at just a few strategic points to know what stage the build is at.
Actually, I see I have already done this, long ago. There is a file named mb4N_hudson.sh which is nearly identical to our cronjob version, mb4N.sh, but does not re-direct output. So, the output going to Hudson's log is only about 6 Megabytes.
This is not quite right, after all. For at least two reasons. One reason the Hudson logs were realtively small is I had set our MVN_DEBUG variable to false (which later controls maven's -X paramter). We normally run with that variable as "true", and when I tried taht, my browser "froze up" after a while because so much ouput was being displayed to to it. The second reason, even with MVN_DEBUG set to false, it seems some very banel output comes to the Hudson console, that really should be being piped to its own "build log". For example, page after page of great detail about "cleaning the git repository". Seems a few lines of output (of the strategic steps) would be more appropriate, but still pipe the output somewhere to a file under "buildlogs" in case we needed to see the detail. Not sure why so much output was coming to the console when MVN_DEBUG set to true (or, technically, just commented out). Seems it should have been going to the "mvn build" output file?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
