Travis Logs processes log updates which are streamed from Travis Worker instances via RabbitMQ. The log parts are streamed via Pusher to the web client (Travis Web) and added to the database.
Once all log parts have been received, and a timeout has passed (10 seconds default), the log parts are aggregated into one final log.
Although Travis Logs is built to archive logs to S3, and vacuum from the database once it is verified that the logs are archived correctly. This has been run for all previous logs prior to January but it not active at the moment.
See LICENSE file.
Copyright (c) 2011 Travis CI development team.