Jenkins’ default logs can be hard to read, but they don’t have to be. By Evan “Hippy” Slatis (Red Hat).
Jenkins is a free and open source automation server for building, testing, and deploying code. It’s the backbone of continuous integration and continuous delivery (CI/CD) and can save developers hours each day and protect them from having failed code go live. When code does fail, or when a developer needs to see the output of tests, Jenkins provides log files for review.
The default Jenkins pipeline logs can be difficult to read. This quick summary of Jenkins logging basics offers some tips (and code) on how to make them more readable:
- What you get
- What can be done?
- Best practices
- Kubernetes Secrets: Where full transparency won’t work
There are some things that you don’t want to end up in your logs and be exposed. If you’re using Kubernetes and referencing data held in a Kubernetes Secret, then you definitely don’t want that data exposed in a log because the data is only obfuscated and not encrypted. Nice one!
[Read More]