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
Mastering Jenkins

You're reading from   Mastering Jenkins Configure and extend Jenkins to architect, build, and automate efficient software delivery pipelines

Arrow left icon
Product type Paperback
Published in Oct 2015
Publisher Packt
ISBN-13 9781784390891
Length 334 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
jmcallister - jmcallister -
Author Profile Icon jmcallister -
jmcallister -
 McAllister McAllister
Author Profile Icon McAllister
McAllister
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Mastering Jenkins
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Setup and Configuration of Jenkins FREE CHAPTER 2. Distributed Builds – Master/Slave Mode 3. Creating Views and Jobs in Jenkins 4. Managing Views and Jobs in Jenkins 5. Advanced Automated Testing 6. Software Deployments and Delivery 7. Build Pipelines 8. Continuous Practices 9. Integrating Jenkins with Other Technologies 10. Extending Jenkins Index

The plugin skeleton


In the previous section we commanded Maven to generate a basic plugin skeleton (hpi:create) structure, and then launched our plugin in a local development sandbox by executing the hpi:run goal. Now that the skeleton structure has been created, let's take a look at the contents of the skeleton structure, and learn about the roles that each of these folders will play in our quest for plugin development:

  • ./src

  • ./target

  • ./work

  • ./pom.xml

From the folder structure described above we can see there are a number of sub-folders, and a POM file. Lets take a minute to examine each of these in greater detail:

  • ./src: This folder contains the source code for the plugin.

  • ./target: This folder contains the compiled binary output (*.hpi) and test execution results output.

  • ./work: This folder is created when the plugin is installed into the sandbox and contains the extracted Java classes and respective temporary working files.

  • pom.xml: This file is the top-level Maven project file, which...

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