|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Is this ever happening when it's not the first build of a job that's downstream from hundreds of programmatically triggered builds that are also #1 of their respective jobs and form a very tightly coupled dependency graph? I mean, 'Admin' triggered many builds that were downstream from a dozen others, which probably only happens once when you initially set up your projects.
Because, if you have such a setup and workflow, and cannot handle a single 100+ MB log file, you're doing something wrong IMO.
What I mean is: You mention that this results in unnecessarily long log files, but don't explain why this is a super serious problem. I regularly have log files in the gigabytes, and while they're somewhat annoying to view (definitely not browser compatible in all their glory) I just download them and I'm good. In the new example, the console tail shown by default includes everything that's relevant. I just don't see the huge problem here. Disk space?