csye7125-fall2023-group05 / ami-jenkins Goto Github PK

• Update scripts/install.sh to install Jenkins and caddy (or nginx) as the reverse proxy server.
• Add SSL certificate to reverse proxy server.

1. Install docker on AMI
2. Update docker daemon permissions

   chmod 666 /var/run/docker.sock

3. Setup jenkins user
4. Install jenkins packages

• Create a Groovy script that will configure/create a multi-branch pipeline for the Webapp Helm Chart that runs the pipeline job defined in the Jenkinsfile in webapp-helm-chart.
• Add tools section to configure nodejs to run SemVer for Jenkins CI/CD pipeline.

• Create a GitHub Actions workflow to run PR-check that will validate the Terraform code before being allowed to merge.

• Any changes pushed to the ami-jenkins repository should trigger a build with a new private AMI being registered with the root AWS account.

• Enable GitHub Status Checks for AMIs

  • Enable GitHub checks on the GitHub repository in your organization.
  • Run packer validate on all pull requests.

• Create user specific environments to run GitHub actions with user defined pkrvars.
• Update the packer-validate.yml (CI) action runner to use GHA environments.
• Add build action runner (CD) for custom AMI.

Install the following software package distributions:

• Helm
• Kubectl
• GCloud CLI
• GCloud GKE Auth Plugin

Jenkins is configured via JCasC, through the AMI created by Packer. We need to successfully configure GitHub wehooks with our Jenkins instance so that we can trigger our build pipelines through seed jobs defined in the JCasC `yaml file.

This needs to be done via the GitHub GUI.

NOTE: Remember to configure DockerHub credentials in order for the Jenkinsfile pipeline script to execute successfully.

@sydrawat01 @rishabNeu

@karanwadhwa need to update the SUBNET_ID secret in your repository environment to pass the CI/CD pipeline for github actions to validate and create a custom AMI for Jenkins.

The latest plugins.txt file does not contain the following plugins required to configure Jenkins with a YAML file and setup seed jobs in Groovy:

• job-dsl
• configuration-as-code-groovy

Also, few seconds of sleep after installing a new apt-get package will generate a much cleaner packer build log output.

Configure the JCasC and Groovy seed files to configure semver CI/CD pipelines.

• Add --quiet option to wget command when downloading the plugin-manager-tool from github.com.
• Update seed job to JCasC template for either multibranch pipeline seed job or github organization folder seed job
• Update list of plugins to be installed. (see comment below for details)
• Update folder structure to move Jenkins related code and config files into a folder jenkins/, and keep the seed job Groovy script in the scripts/ folder. JCasC file should be in jenkins/ folder as well.
• [BUG] Fix Packer file provisioner to copy the JCasC file into /home/ubuntu,and use the install.sh script to move the file to Jenkins home, i.e., /var/lib/jenkins/ (use sudo) and update user & group to jenkins
  • sudo chown jenkins:jenkins /var/lib/jenkins/jcasc.yaml

• Use split() function provided by HCP Packer to split a single string of comma separated AWS user IDs.
• Use the result of the split() function as the value in the ami_users option for the amazon-ebs source definition.

split() docs

• Update README.md to include steps to configure and install HCP Packer locally to create custom AMIs.
• Use pkrvars to provide dynamic variables instead of hard-coding them.
• Create a sample pkrvars.hcl variables file that will list out all the variables being used in the packer config file.
• Create a simple provisioner that will run though a shell script [scripts/install.sh].

Add required plugins to AMI for Jenkins

Configure user credentials through JCasC. Make sure to not hardcode the values anywhere, along with the Groovy seed job scripts to use variables and secrets passed through to the JCasC and Groovy files/scripts.