Truncating The Logs

Wercker is a Docker-Native CI/CD Automation platform for Kubernetes & Microservice Deployments

Benno van den berg
Benno van den berg
June 4, 2014

We’ve made some modifications to the logging system on wercker. From now on logs will be limited to 1500000 bytes per buildstep. So this is about 1,4 megabytes. Most users will never reach this number, however there were a few instances where users did exceed this number.

Logs truncation

If your logs exceed the maximum length, then we will start truncating from the beginning of the logs for that buildstep and add a message to the beginning of the logs. Usually the end of a log contains a summary, which is why we want to show that part, and not the beginning. If your logs are being truncated, then try to make lessen the output of the step less. For unit tests you might want to change reporters, or in your application change the log levels.

Also note that command characters count to the log. These characters can change the colors of the shell or overwrite previous printed characters. Don’t worry about color in output of unit test runners or similar steps, but be careful with fancy reporters. We recommend using simple reporters, such as progress for rspec.

Earn some stickers!

Let us know about the applications you build with wercker. Don’t forget to tweet out a screenshot of your first green build with #wercker and we’ll send you some @wercker stickers.

Follow us on twitter as well to stay in the loop.



Topics: Product