Skip to content

This Project is to Automate Provisioning and Integration of Jenkins, Nexus & SonarQube

Notifications You must be signed in to change notification settings

yogeshgunasekaran/Automated-Provisioning-Project-2

Repository files navigation

Automated-Provisioning-Project-2

This Project is to Automate Provisioning of Jenkins, Nexus & SonarQube

Prerequisite - 3 AWS EC2 Instances

Note : Create all the three servers in same availabilty zone under a VPC, resulting in creating a network so that the private IP can used for the system communication.

1. Jenkins Server

  • AMI - Ubuntu 20.04 LTS
  • Instance type - t2 small - 1 vCPU - 2 GB Memory
  • Security Group,
    • Allow port 22, source: My IP - to ssh into jenkins server from My IP
    • Allow port 8080, source: My IP - to access jenkins on web from My IP
    • Allow port 8080, source: SonarQube-Security-Group - for sonarqube to connect with jenkins for quality check

2. Nexus Server

  • AMI - CentOS7 LTS
  • Instance type - t2 medium - 2 vCPU - 4 GB Memory
  • Security Group,
    • Allow port 22, source: My IP - to ssh into nexus server from My IP
    • Allow port 8081, source: Jenkins-Security-Group - to access nexus on web from My IP and also for jenkins to access it on command line

3. SonarQube Server

  • AMI - Ubuntu 20.04 LTS
  • Instance type - t2 medium - 2 vCPU - 4 GB Memory
  • Security Group,
    • Allow port 22, source: My IP - to ssh into sonarqube server from My IP
    • Allow port 9000, source: My IP - to access sonarqube on web from My IP
    • Allow port 9000, source: Jenkins-Security-Group - for jenkins to access sonarqube
    • Allow port 80, source: My IP - to access sonarqube on web from My IP (this is through ngnix reverse proxy)

About

This Project is to Automate Provisioning and Integration of Jenkins, Nexus & SonarQube

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages