Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Extending Jenkins

You're reading from   Extending Jenkins Get a complete walkthrough of the many interfaces available in Jenkins with the help of real-world examples to take you to the next level with Jenkins

Arrow left icon
Product type Paperback
Published in Dec 2015
Publisher
ISBN-13 9781785284243
Length 152 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
 Simpson Simpson
Author Profile Icon Simpson
Simpson
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Extending Jenkins
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
1. Preparatory Steps FREE CHAPTER 2. Automating the Jenkins UI 3. Jenkins and the IDE 4. The API and the CLI 5. Extension Points 6. Developing Your Own Jenkins Plugin 7. Extending Jenkins Plugins 8. Testing and Debugging Jenkins Plugins 9. Putting Things Together Index

Summary


In this chapter, we looked at the concepts behind several major design patterns and saw when you would use each approach and why you would do so.

If you are an experienced Java programmer, these concepts should be very familiar, and if not, then hopefully this will serve as a foundation that will help you to understand not only what we are doing in the subsequent chapters, but also why we are doing it.

In the beginning of this chapter, we touched upon the philosophy behind plugin development—that people should seek to collaborate, reuse, and extend existing code to provide new functionality whenever possible. If everyone went off and created their own plugins for their own particular needs, rather than collaborating and contributing to existing efforts, there would be massive duplication and replication, and the quality would be far poorer as a result.

This ethos and the preceding design approach has created a community of plugin developers who produce high quality software by providing...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images