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
Jenkins 2.x Continuous Integration Cookbook

You're reading from   Jenkins 2.x Continuous Integration Cookbook Over 90 recipes to produce great results using pro-level practices, techniques, and solutions

Arrow left icon
Product type Paperback
Published in Oct 2017
Publisher Packt
ISBN-13 9781788297943
Length 438 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Mitesh Soni Mitesh Soni
Author Profile Icon Mitesh Soni
Mitesh Soni
 Berg Berg
Author Profile Icon Berg
Berg
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Title Page
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Dedication
Preface
1. Getting Started with Jenkins FREE CHAPTER 2. Management and Monitoring of Jenkins 3. Managing Security 4. Improving Code Quality 5. Building Applications in Jenkins 6. Continuous Delivery 7. Continuous Testing 8. Orchestration 9. Jenkins UI Customization 10. Processes that Improve Quality

Verifying Java code using SonarQube


Now let's a new Quality Profile and assign the project so every time static code analysis is performed, the default profile is not but a custom profile is utilized.

Getting ready

  1. Go to Quality Profiles and in the Java section, copy the default profile:

  1. Give a specific name to it and click on Copy:
  1. We can specify projects for a specific Quality Profile by clicking on Change Projects as well:
  1. Assign a Quality Profile to your project so that the same profile is used every time a static code analysis is performed. Hence, we can use different profiles for different projects based on our requirements.

How to do it...

  1. Go to the Jenkins dashboard and click on New Item.
  2. Give the Name and select Freestyle project.
  3. Provide the Repository URL in the Source Code Management section.
  4. Go to the Build section and select Execute SonarQube Scanner.
  5. You can provide the location of sonar-project.properties or provide details directly for static code analysis:
# Required metadata sonar...
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