Have you ever heard someone mention the name Jenkins when developing an app and thought to yourself, who the hell is that?
In plain English, you can use Jenkins to build and test your software projects. This makes it easier for developers to identify and integrate changes into a design. The concept of Jenkins is that it will provide developers with fast feedback on development builds as they happen. This is useful as Jenkins can inform developers of when a build has been broken, how it broke, and how they can revert it back to working order.
If a developer was to only run tests from time to time, they’ll soon find that there would be extensive amounts of code added since the last test was run. This means that if the build was to break within that time frame, it could be difficult to backtrack and identify what caused the issue. This is where Jenkins comes into play.
‘In Plain English’ is a series that, in 200 words or less, describes technical “jargon” in a non-technical way. The descriptions aim to provide ‘just enough’ detail to allow non-technical stakeholders to understand and contribute to, high-level technical discussions.