What happened to stdout on CI?

February 14, 2013 Mark Rushakoff

We were struggling for a bit yesterday trying to figure out why the few puts statements in our tests weren’t being displayed in Jenkins’ console output.

It turns out the ci_reporter gem that we were using (so that Jenkins could parse our test results) swallows stdout and stderr by default — unless you set the CI_CAPTURE environment variable to the string "off", like it tells you to do in the readme.

That was a confusing default setting. Since my pair and I weren’t involved in setting up Jenkins, and we didn’t install the ci_reporter gem, we assumed something was misconfigured in Jenkins before we started digging through the code.

Hopefully this saves someone else some time!

About the Author

Biography

More Content by Mark Rushakoff
Previous
10 Reasons Why Hadoop Will Dominate in 2013
10 Reasons Why Hadoop Will Dominate in 2013

The Apache Hadoop platform has been ascendant in recent years, thanks to its flexibility, rich developer ec...

Next
Using ActiveRecord with multiple databases
Using ActiveRecord with multiple databases

At Pivotal I’ve been working on a project which uses two databases. Doing some quick searching we came up w...

Enter curious. Exit smarter.

Learn More