You're reading from Learning Continuous Integration with Jenkins An end-to-end guide to creating operational, secure, resilient, and cost-effective CI/CD processes

Product type Paperback

Published in Jan 2024

Publisher Packt

ISBN-13 9781835087732

Length 396 pages

Edition 3rd Edition

Tools

Jenkins

Concepts

Continuous Integration

Author (1):

Nikhil Pathania

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1: The Concepts FREE CHAPTER

2. Chapter 1: The What, How, and Why of Continuous Integration

3. Part 2: Engineering the CI Ecosystem

4. Chapter 2: Planning, Deploying, and Maintaining Jenkins

5. Chapter 3: Securing Jenkins

6. Chapter 4: Extending Jenkins

7. Chapter 5: Scaling Jenkins

8. Part 3: Crafting the CI Pipeline

9. Chapter 6: Enhancing Jenkins Pipeline Vocabulary

10. Chapter 7: Crafting AI-Powered Pipeline Code

11. Chapter 8: Setting the Stage for Writing Your First CI Pipeline

12. Chapter 9: Writing Your First CI Pipeline

13. Part 4: Crafting the CD Pipeline

14. Chapter 10: Planning for Continuous Deployment

15. Chapter 11: Writing Your First CD Pipeline

16. Chapter 12: Enhancing Your CI/CD Pipelines

17. Index

Why subscribe?

18. Other Books You May Enjoy

Connecting Jenkins to Artifactory

This section describes setting up an Artifactory server using a Helm chart. We will deploy it on the same AKS cluster where our Jenkins and SonarQube server runs but in a different namespace. Our Artifactory server will have an Nginx Ingress controller in front of it with its own public IP. To keep things simple, we will avoid going into the details of setting up a production-grade Artifactory setup with detailed user access and permissions. So, let’s start.

Deploying an Nginx Ingress controller for Artifactory

Just like for SonarQube, we will create an Nginx Ingress controller for Artifactory too. Take the following steps:

Connect to your AKS cluster. Use the Azure CLI (`az`) or Azure portal to authenticate and connect to your AKS cluster.
Execute the following two commands one after the other to add the ingress-nginx repository as a source of Helm charts and update the local cache to have the latest information on the available...