Spelling & Grammar Day 71-80

Abhiricky · Jun 26, 2022 · bf051de · bf051de
1 parent 6963d26
commit bf051de
Show file tree

Hide file tree

Showing 10 changed files with 147 additions and 147 deletions.
diff --git a/Days/day71.md b/Days/day71.md
@@ -2,46 +2,46 @@
 title: '#90DaysOfDevOps - What is Jenkins? - Day 71'
 published: false
 description: 90DaysOfDevOps - What is Jenkins?
-tags: 'devops, 90daysofdevops, learning'
+tags: 'DevOps, 90daysofdevops, learning'
 cover_image: null
 canonical_url: null
 id: 1048745
 ---
 
 ## What is Jenkins?
 
-Jenkins is a continuous integration tool that allows continuous development, test and deployment of newly created code.
+Jenkins is a continuous integration tool that allows continuous development, testing and deployment of newly created code.
 
-There are two ways we can achieve this with either nightly builds or continuous development. The first option is that our developers are developing throughout the day on their tasks and come the end of the set day they push their changes to the source code repository. Then during the night we run our unit tests and build of the software. This could be deemed as the old way to integrate all code.
+There are two ways we can achieve this with either nightly builds or continuous development. The first option is that our developers are developing throughout the day on their tasks and come to the end of the set day they push their changes to the source code repository. Then during the night we run our unit tests and build the software. This could be deemed as the old way to integrate all code.
 
 ![](Images/Day71_CICD1.png)
 
 The other option and the preferred way is that our developers are still committing their changes to source code, then when that code commit has been made there is a build process kicked off continuously.
 
 ![](Images/Day71_CICD2.png)
 
-The above methods means that with distributed developers across the world we don't have a set time each day where we have to stop committing our code changes. This is where Jenkins comes in to act as that CI server to control those tests and build processes.
+The above methods mean that with distributed developers across the world we don't have a set time each day where we have to stop committing our code changes. This is where Jenkins comes in to act as that CI server to control those tests and build processes.
 
 ![](Images/Day71_CICD3.png)
 
-I know we are talking about Jenkins here but I also want to add a few more to maybe look into later on down the line to get an understanding why I am seeing Jenkins as the overall most popular, why is that and what can the others do over Jenkins.
+I know we are talking about Jenkins here but I also want to add a few more to maybe look into later on down the line to get an understanding of why I am seeing Jenkins as the overall most popular, why is that and what can the others do over Jenkins.
 
 - TravisCI - A hosted, distributed continuous integration service used to build and test software projects hosted on GitHub.
-- Bamboo - Can run multiple builds in parallel for faster compilation, built in functionality to connect with repositories and has build tasks for Ant, Maven.
+- Bamboo - Can run multiple builds in parallel for faster compilation, built-in functionality to connect with repositories and has build tasks for Ant, and Maven.
 - Buildbot - is an open-source framework for automating software build, test and release processes. It is written in Python and supports distributed, parallel execution of jobs across multiple platforms.
-- Apache Gump - Specific to Java projects, designed with the aim to build and test those Java projects every night. ensures that all projects are compatible at both API and functionality level.
+- Apache Gump - Specific to Java projects, designed to build and test those Java projects every night. ensures that all projects are compatible at both API and functionality levels.
 
-Because we are now going to focus on Jenkins - Jenkins is again open source like all of the above tools and is an automation server written in Java. It is used to automate the software development process via continuous integration adn facilitates continuous delivery.
+Because we are now going to focus on Jenkins - Jenkins is again open source like all of the above tools and is an automation server written in Java. It is used to automate the software development process via continuous integration and facilitates continuous delivery.
 
 ### Features of Jenkins
 
 As you can probably expect Jenkins has a lot of features spanning a lot of areas.
 
-**Easy Installation** - Jenkins is a self contained java based program ready to run with packages for Windows, macOS and Linux operating systems.
+**Easy Installation** - Jenkins is a self-contained java based program ready to run with packages for Windows, macOS and Linux operating systems.
 
-**Easy Configuration** - Easy setup and configured via a web interface which includes error checks and built in help.
+**Easy Configuration** - Easy setup and configuration via a web interface which includes error checks and built-in help.
 
-**Plug-ins** - Lots of plugins available in the Update Centre and integrates with many tools in the CI / CD toolchain.
+**Plug-ins** - Lots of plugins are available in the Update Centre and integrate with many tools in the CI / CD toolchain.
 
 **Extensible** - In addition to the Plug-Ins available, Jenkins can be extended by that plugin architecture which provides nearly infinite options for what it can be used for.
 
@@ -69,27 +69,27 @@ Step 1 - Developers commit changes to the source code repository.
 
 Step 2 - Jenkins checks the repository at regular intervals and pulls any new code.
 
-Step 3 - A build server then builds the code into an executable, in this example we are using maven as a well known build server. Another area to cover.
+Step 3 - A build server then builds the code into an executable, in this example, we are using maven as a well-known build server. Another area to cover.
 
 Step 4 - If the build fails then feedback is sent back to the developers.
 
-Step 5 - Jenkins then deploys the build app to the test server, in this example we are using selenium as a well known test server. Another area to cover.
+Step 5 - Jenkins then deploys the build app to the test server, in this example, we are using selenium as a well-known test server. Another area to cover.
 
 Step 6 - If the test fails then feedback is passed to the developers.
 
-Step 7 - If the tests are successful then we can release to production.
+Step 7 - If the tests are successful then we can release them to production.
 
-This cycle is continuous, this is what allows applications to be updated in minutes vs hours, days, months, years!
+This cycle is continuous, this is what allows applications to be updated in minutes vs hours, days, months, and years!
 
 ![](Images/Day71_CICD5.png)
 
-There is a lot more to the architecture of Jenkins if you require it, they have a master-slave capability, which enables a master to distribute the tasks to slave jenkins environment.
+There is a lot more to the architecture of Jenkins if you require it, they have a master-slave capability, which enables a master to distribute the tasks to the slave Jenkins environment.
 
 For reference with Jenkins being open source, there are going to be lots of enterprises that require support, CloudBees is that enterprise version of Jenkins that brings support and possibly other functionality for the paying enterprise customer.
 
 An example of this in a customer is Bosch, you can find the Bosch case study [here](https://assets.ctfassets.net/vtn4rfaw6n2j/case-study-boschpdf/40a0b23c61992ed3ee414ae0a55b6777/case-study-bosch.pdf)
 
-I am going to be looking for a step by step example of an application that we can use to walkthrough using Jenkins and then also use this with some other tools.
+I am going to be looking for a step-by-step example of an application that we can use to walk through using Jenkins and then also use this with some other tools.
 
 ## Resources
 
@@ -102,4 +102,4 @@ I am going to be looking for a step by step example of an application that we ca
 - [GitHub Actions](https://www.youtube.com/watch?v=R8_veQiYBjI)
 - [GitHub Actions CI/CD](https://www.youtube.com/watch?v=mFFXuXjVgkU)
 
-See you on [Day 72](day72.md)
+See you on [Day 72](day72.md)
diff --git a/Days/day72.md b/Days/day72.md
@@ -1,16 +1,16 @@
 ---
-title: '#90DaysOfDevOps - Getting hands on with Jenkins - Day 72'
+title: '#90DaysOfDevOps - Getting hands-on with Jenkins - Day 72'
 published: false
-description: 90DaysOfDevOps - Getting hands on with Jenkins
-tags: 'devops, 90daysofdevops, learning'
+description: 90DaysOfDevOps - Getting hands-on with Jenkins
+tags: 'DevOps, 90daysofdevops, learning'
 cover_image: null
 canonical_url: null
 id: 1048829
 ---
 
-## Getting hands on with Jenkins
+## Getting hands-on with Jenkins
 
-The plan today is to get some hands on with Jenkins and make something happen as part of our CI pipeline, looking at some example code bases that we can use.
+The plan today is to get some hands-on with Jenkins and make something happen as part of our CI pipeline, looking at some example code bases that we can use.
 
 ### What is a pipeline?
 
@@ -20,19 +20,19 @@ Before we start we need to know what is a pipeline when it comes to CI, and we a
 
 We want to take the processes or steps above and we want to automate them to get an outcome eventually meaning that we have a deployed application that we can then ship to our customers, end users etc.
 
-This automated process enables us to have a version control through to our users and customers. Every change, feature enhancement, bug fix etc goes through this automated process confirming that everything is fine without too much manual intervention to ensure our code is good.
+This automated process enables us to have version control through to our users and customers. Every change, feature enhancement, bug fix etc goes through this automated process confirming that everything is fine without too much manual intervention to ensure our code is good.
 
 This process involves building the software in a reliable and repeatable manner, as well as progressing the built software (called a "build") through multiple stages of testing and deployment.
 
-A jenkins pipeline, is written into a text file called a Jenkinsfile. Which itself should be committed to a source control repository. This is also known as Pipeline as code, we could also very much liken this to Infrastructure as code which we covered a few weeks back.
+A Jenkins pipeline is written into a text file called a Jenkinsfile. Which itself should be committed to a source control repository. This is also known as Pipeline as code, we could also very much liken this to Infrastructure as code which we covered a few weeks back.
 
 [Jenkins Pipeline Definition](https://www.jenkins.io/doc/book/pipeline/#ji-toolbar)
 
 ### Deploying Jenkins
 
 I had some fun deploying Jenkins, You will notice from the [documentation](https://www.jenkins.io/doc/book/installing/) that there are many options on where you can install Jenkins.
 
-Given that I have minikube on hand and we have used this a number of times I wanted to use this for this task also. (also it is free!) Although the steps given in the [Kubernetes Installation](https://www.jenkins.io/doc/book/installing/kubernetes/) had me hitting a wall and not getting things up and running, you can compare the two when I document my steps here.
+Given that I have minikube on hand and we have used this several times I wanted to use this for this task also. (also it is free!) Although the steps are given in the [Kubernetes Installation](https://www.jenkins.io/doc/book/installing/kubernetes/) had me hitting a wall and not getting things up and running, you can compare the two when I document my steps here.
 
 The first step is to get our minikube cluster up and running, we can simply do this with the `minikube start` command.
 
@@ -42,33 +42,33 @@ I have added a folder with all the YAML configuration and values that can be fou
 
 ![](Images/Day72_CICD2.png)
 
-We will be using Helm to deploy jenkins into our cluster, we covered helm in the Kubernetes section. We firstly need to add the jenkinsci helm repository `helm repo add jenkinsci https://charts.jenkins.io` then update our charts `helm repo update`.
+We will be using Helm to deploy Jenkins into our cluster, we covered helm in the Kubernetes section. We first need to add the jenkinsci helm repository `helm repo add jenkinsci https://charts.jenkins.io` then update our charts `helm repo update`.
 
 ![](Images/Day72_CICD3.png)
 
 The idea behind Jenkins is that it is going to save state for its pipelines, you can run the above helm installation without persistence but if those pods are rebooted, changed or modified then any pipeline or configuration you have made will be lost. We will create a volume for persistence using the jenkins-volume.yml file with the `kubectl apply -f jenkins-volume.yml` command.
 
 ![](Images/Day72_CICD4.png)
 
-We also need a service account which we can create using this yaml file and command. `kubectl apply -f jenkins-sa.yml`
+We also need a service account which we can create using this YAML file and command. `kubectl apply -f jenkins-sa.yml`
 
 ![](Images/Day72_CICD5.png)
 
-At this stage we are good to deploy using the helm chart, we will firstly define our chart using `chart=jenkinsci/jenkins` and then we will deploy using this command where the jenkins-values.yml contain the persistence and service accounts that we previously deployed to our cluster. `helm install jenkins -n jenkins -f jenkins-values.yml $chart`
+At this stage we are good to deploy using the helm chart, we will first define our chart using `chart=jenkinsci/jenkins` and then we will deploy using this command where the jenkins-values.yml contain the persistence and service accounts that we previously deployed to our cluster. `helm install jenkins -n jenkins -f jenkins-values.yml $chart`
 
 ![](Images/Day72_CICD6.png)
 
-At this stage our pods will be pulling the image but the pod will not have access to the storage so no configuration can be started in terms of getting Jenkins up and running.
+At this stage, our pods will be pulling the image but the pod will not have access to the storage so no configuration can be started in terms of getting Jenkins up and running.
 
-This is where the documentation did not help me massively understand what needed to happen. But we can see that we have no permission to start our jenkins install.
+This is where the documentation did not help me massively understand what needed to happen. But we can see that we have no permission to start our Jenkins install.
 
 ![](Images/Day72_CICD7.png)
 
-In order to fix the above or resolve, we need to make sure we provide access or the right permission in order for our jenkins pods to be able to write to this location that we have suggested. We can do this by using the `minikube ssh` which will put us into the minikube docker container we are running on, and then using `sudo chown -R 1000:1000 /data/jenkins-volume` we can ensure we have permissions set on our data volume.
+To fix the above or resolve it, we need to make sure we provide access or the right permission for our Jenkins pods to be able to write to this location that we have suggested. We can do this by using the `minikube ssh` which will put us into the minikube docker container we are running on, and then using `sudo chown -R 1000:1000 /data/jenkins-volume` we can ensure we have permissions set on our data volume.
 
 ![](Images/Day72_CICD8.png)
 
-The above process should fix the pods, however if not you can force the pods to be refreshed with the `kubectl delete pod jenkins-0 -n jenkins` command. At this point you should have 2/2 running pods called jenkins-0.
+The above process should fix the pods, however, if not you can force the pods to be refreshed with the `kubectl delete pod jenkins-0 -n jenkins` command. At this point, you should have 2/2 running pods called jenkins-0.
 
 ![](Images/Day72_CICD9.png)
 
@@ -80,7 +80,7 @@ Now open a new terminal as we are going to use the `port-forward` command to all
 
 ![](Images/Day72_CICD11.png)
 
-We should now be able to open a browser and login to `http://localhost:8080` and authenticate with the username: admin and password we gathered in a previous step.
+We should now be able to open a browser and log in to `http://localhost:8080` and authenticate with the username: admin and password we gathered in a previous step.
 
 ![](Images/Day72_CICD12.png)
 
@@ -92,13 +92,13 @@ From here, I would suggest heading to "Manage Jenkins" and you will see "Manage
 
 ![](Images/Day72_CICD14.png)
 
-If you want to go even further and automate the deployment of Jenkins using a shell script this great repository was shared with me on twitter [mehyedes/nodejs-k8s](https://github.com/mehyedes/nodejs-k8s/blob/main/docs/automated-setup.md)
+If you want to go even further and automate the deployment of Jenkins using a shell script this great repository was shared with me on Twitter [mehyedes/nodejs-k8s](https://github.com/mehyedes/nodejs-k8s/blob/main/docs/automated-setup.md)
 
 ### Jenkinsfile
 
 Now we have Jenkins deployed in our Kubernetes cluster, we can now go back and think about this Jenkinsfile.
 
-Every Jenkinsfile will likely start like this, Which is firstly where you would define your steps of your pipeline, in this instance you have Build > Test > Deploy. But we are not really doing anything other than using the `echo` command to call out the specific stages.
+Every Jenkinsfile will likely start like this, Which is firstly where you would define the steps of your pipeline, in this instance you have Build > Test > Deploy. But we are not doing anything other than using the `echo` command to call out the specific stages.
 
 ```
 
@@ -132,7 +132,7 @@ In our Jenkins dashboard, select "New Item" give the item a name, I am going to
 
 ![](Images/Day72_CICD15.png)
 
-Hit Ok and you will then have the tabs (General, Build Triggers, Advanced Project Options and Pipeline) for a simple test we are only interested in Pipeline. Under Pipeline you have the ability to add a script, we can copy and paste the above script into the box.
+Hit Ok and you will then have the tabs (General, Build Triggers, Advanced Project Options and Pipeline) for a simple test we are only interested in Pipeline. Under Pipeline you can add a script, we can copy and paste the above script into the box.
 
 As we said above this is not going to do much but it will show us the stages of our Build > Test > Deploy
 
@@ -146,9 +146,9 @@ We should also open a terminal and run the `kubectl get pods -n jenkins` to see
 
 ![](Images/Day72_CICD18.png)
 
-Ok, very simple stuff but we can now see that our Jenkins deployment and installation is working correctly and we can start to see the building blocks of the CI pipeline here.
+Ok, very simple stuff but we can now see that our Jenkins deployment and installation are working correctly and we can start to see the building blocks of the CI pipeline here.
 
-In the next section we will be building a Jenkins Pipeline.
+In the next section, we will be building a Jenkins Pipeline.
 
 ## Resources
 
@@ -161,4 +161,4 @@ In the next section we will be building a Jenkins Pipeline.
 - [GitHub Actions](https://www.youtube.com/watch?v=R8_veQiYBjI)
 - [GitHub Actions CI/CD](https://www.youtube.com/watch?v=mFFXuXjVgkU)
 
-See you on [Day 73](day73.md)
+See you on [Day 73](day73.md)