I’ve been reading some threads around logs and they all seem to describe issues similar to this one, but they are not the same. I’ve also seen that there were some logs limits in the agent of 0.5, but I browsed through the code and didn’t find in 0.8.
drone limits the amount of logs to 2MB per pipeline step to prevent a single step from overloading the logs and freezing the browser, and potentially causing OOM issues since logs are streamed from memory while the build is running. Do you have the option to reduce logging verbosity? Or split tests into multiple steps, thus removing the per-step limit?
Not at the moment. This is something we could make configurable in the future, but it would not be until the next release.
You could pipe the results to a file and upload them somewhere (to S3) in the subsequent step.
- set -o pipefail
- go get -t ./...
- go test -v ./... | tee gotest.out
secrets: [ aws_access_key_id, aws_secret_access_key ]
Exposing secrets, however, to public pull requests is not recommended unless you enable the “protected” repository setting (screenshot below). This setting will block pull requests that change the yaml and require manual approval, to prevent tampering with the yaml in an attempt to expose secrets.
Thank you @bradrydzewski, I’ll certainly try that out. I was aware that was a possibility, but wanted to know if there was some way of avoiding it because of the layer of indirection it adds to the build.
In the future, it would be great if Drone was a little bit more configurable than it is right now so that all these use cases can be accommodated. I would be happy to have some kind of link to download the logs if they are too large rather than seeing them (this is to the best of my understanding what Jenkinds does).