Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Watch Me Code, Episode 6 [Video]

DZone's Guide to

Watch Me Code, Episode 6 [Video]

This coding video continues the series by focusing on Organization folder functionality and the use of third-party libraries from Jenkins plugins.

· DevOps Zone ·
Free Resource

Is the concept of adopting a continuous everything model a daunting task for your fast moving business? Read this whitepaper to break down and understand one of the key pillars of this model in Continuous Governance: The Guardrails for Continuous Everything.

Episode 4 and Episode 5 of "Watch Me Code" were focused on the Jenkinsfile techniques we will need when we start using the Organization folder that we developed in Episode 3. This episode returns focus to that Organization folder functionality. When we left the plugin last, we had a plugin that was functional, but not as efficient as it could be. In order to make a better Organization folder, we will need to make use of some of third-party libraries.


This episode covers two strategies for using third-party libraries from Jenkins plugins.

I also tacking upgrading the parent pom in order to take advantage of the latest tooling improvements. By the end of this video, we should have a plugin code base that is ready for us to rapidly develop the performance improvements we need before putting the plugin into production use on the Apache Software Foundation's Jenkins instance.

If you are interested in examining my work so far, you can look at the GitHub code snapshot as of the end of the video.

Check out the entire series:

Are you looking for greater insight into your software development value stream? Check out this whitepaper: DevOps Performance: The Importance of Measuring Throughput and Stability to see how CloudBees DevOptics can give you the visibility to improve your continuous delivery process.

Topics:
devops ,programming

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}