Details
-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
standalone, jdk1.6.0_23, x86_64 GNU/Linux
-
0
-
Description
I have an enhancement request. I would like the ability to have some sort of configuration entry somewhere (whether on the task, plan, or system level) which will allow me to have Bamboo automatically zip/gzip/lzma logfiles from the build for storage purposes... and to read the logs, it would go through an expansion as required before sending to the client viewing the log.
I understand that it would be the administrator's choice to enable/disable the feature knowing the performance implications.
Here is an example of a build I know would certainly benefit.
bamboo:/somedirectory/bamboo-home/xml-data/builds/SYSTEM-PROJECTNAME-JOB1/download-data/build_logs$ du -sh *
31M SYSTEM-PROJECTNAME-JOB1-10.log
31M SYSTEM-PROJECTNAME-JOB1-11.log
32M SYSTEM-PROJECTNAME-JOB1-12.log
32M SYSTEM-PROJECTNAME-JOB1-13.log
548M SYSTEM-PROJECTNAME-JOB1-14.log
548M SYSTEM-PROJECTNAME-JOB1-15.log
16M SYSTEM-PROJECTNAME-JOB1-16.log
544M SYSTEM-PROJECTNAME-JOB1-17.log
541M SYSTEM-PROJECTNAME-JOB1-18.log
540M SYSTEM-PROJECTNAME-JOB1-19.log
37M SYSTEM-PROJECTNAME-JOB1-1.log
4.9M SYSTEM-PROJECTNAME-JOB1-20.log
546M SYSTEM-PROJECTNAME-JOB1-21.log
546M SYSTEM-PROJECTNAME-JOB1-22.log
543M SYSTEM-PROJECTNAME-JOB1-23.log
529M SYSTEM-PROJECTNAME-JOB1-24.log
539M SYSTEM-PROJECTNAME-JOB1-25.log
540M SYSTEM-PROJECTNAME-JOB1-26.log
540M SYSTEM-PROJECTNAME-JOB1-27.log
540M SYSTEM-PROJECTNAME-JOB1-28.log
547M SYSTEM-PROJECTNAME-JOB1-29.log
37M SYSTEM-PROJECTNAME-JOB1-2.log
4.0K SYSTEM-PROJECTNAME-JOB1-30.log
8.0K SYSTEM-PROJECTNAME-JOB1-31.log
37M SYSTEM-PROJECTNAME-JOB1-3.log
12M SYSTEM-PROJECTNAME-JOB1-4.log
37M SYSTEM-PROJECTNAME-JOB1-5.log
37M SYSTEM-PROJECTNAME-JOB1-6.log
37M SYSTEM-PROJECTNAME-JOB1-7.log
37M SYSTEM-PROJECTNAME-JOB1-8.log
31M SYSTEM-PROJECTNAME-JOB1-9.log
gzipping the 547M one brought the size down to 23M.
Attachments
Issue Links
- duplicates
-
BAM-2680 Build logs should be compressed
- Gathering Interest