Artifacts and Test Results

Part of the Jenkins course

The build went red at 2am and somebody has to work out why. They open the job, and the only thing on the page is a link to a console log: eleven thousand lines of compiler noise, test runner chatter and shell tracing. Somewhere in there is the name of the one test that broke. That is a pipeline printing green or red and telling you nothing else.

Three steps change that entirely. Publish your artifacts, publish your test results, publish your HTML reports, and the job page starts answering questions on its own: what came out of this build, which tests failed, how coverage moved. This lesson covers all three. ...