Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Continuous Integration, Delivery, and Deployment

You're reading from   Continuous Integration, Delivery, and Deployment Reliable and faster software releases with automating builds, tests, and deployment

Arrow left icon
Product type Paperback
Published in Oct 2017
Publisher Packt
ISBN-13 9781787286610
Length 458 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Sander Rossel Sander Rossel
Author Profile Icon Sander Rossel
Sander Rossel
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Continuous Integration, Delivery, and Deployment Foundations FREE CHAPTER 2. Setting Up a CI Environment 3. Version Control with Git 4. Creating a Simple JavaScript App 5. Testing Your JavaScript 6. Automation with Gulp 7. Automation with Jenkins 8. A NodeJS and MongoDB Web App 9. A C# .NET Core and PostgreSQL Web App 10. Additional Jenkins Plugins 11. Jenkins Pipelines 12. Testing a Web API 13. Continuous Delivery 14. Continuous Deployment

Setting up SonarQube

Now that we can run our Gulp tasks and trigger a build automatically on commit, it is time to add the next step towards quality code, SonarQube. We have already installed, configured, and used SonarQube in Chapter 2, Setting Up a CI Environment, so I assume you have it ready for use. If things do not work, be sure to review Chapter 2, Setting Up a CI Environment, and the part on SonarQube in particular. Here is a little reminder: SonarQube is accessible on ciserver:9000. So, go to your project configuration and add the Execute SonarQube Scanner build step. Put the following configuration in the Analysis Properties field:

sonar.projectKey=chapter7
sonar.projectName=Chapter 7
sonar.projectVersion=1.0

sonar.sources=.

sonar.exclusions=node_modules/**, prod/**, scripts/bundles/**, test/**

I strongly suggest you exclude node_modules (because these are not your files...

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 $19.99/month. Cancel anytime