Published in


My Jenkins Story: Writing a Jenkins Shared Library

When i first came to know of about Jenkins Shared Library, my thoughts were that it is an opportunity to abstract away common pipeline code that can be reused by many pipelines without having to repeat the same code definitions in your pipeline code. Thus making your pipelines more ‘DRY’ (Don’t Repeat Yourself).




Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

Cloud Endpoints

Famous Interview Questions from IT/CS Branch

Applying CSS Animation on Text Elements

Going serverless: Your first AWS Lambda

How to create a team management bot for Discord

Adding SSL to Grafana

Top 6 Common Mistakes to Avoid When Building an API

Skills required to become a Frontend Developer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Colin But

Colin But

Writer sharing thoughts on pretty much everything. P.S. I’m a Coffee-Addict ☕ You can support me by buying me a coffee:

More from Medium

[Workaround] Let's solve the Jenkins slave connection issue with the Jenkins Kubernetes plugin

GitOps Part 2.1: A GitOps Example “Conceptual Expression of Module Based Git Flow”

Deploying Apps to a Local K3d Cluster

Grafana with Azure AD Authentication