In this weeks blog post we'll be covering Jenkins. If you've been following my journey so far you'll notice I've been looking into the world of Dev Ops. A term I've come across frequently is the idea of CI/CD. Jenkins can be used to implement CI/CD, it's the leading open source automation server. With the ability to provide you with 1000's of different plugins to suit your needs.
What is CI/CD?
CI stands for continuous integration - the idea of Continuous Integration (CI) is the idea that you and your team would commit your code little and often in some form of repository (eg git). Each developer would have their own branch and then commit their changes into a shared version. When they commit their code it will trigger an automated build to grab the latest code and then be able to build, test and validate the full repo. The job of a CI server could be to notify you of errors should any be encountered. Say you have been working on something for 6 months and another developer has also been working on something else- when it comes to you both checking in your changes at the same time you might find your code is highly incompatible- you have all types of conflicts left right and centre because your code as so many differences. It's now someone's job to go in and resolve all these conflicts manually (Known as Merge Hell!). So you can see with CI has become very popular!
CD stands for continuous development/delivery. Continuous Delivery gives you the ability to automate your release process and also deploy your application at any given time by clicking a button. Continuous Development goes one step further than continuous delivery by completely automating the process- there is no human interaction what's so ever. Through your code pipelines software is automatically released to production (as long as it passes the relevant tests).
Install Jenkins on your local PC using docker
in this example we'll be using an ubuntu terminal to install. But if your using windows you can follow the same steps by running powershell as admin and removing the word sudo from the commands.
1.) You'll need to pull down the latest Jenkins file to do this run the following:
Sudo Docker pull jenkins/jenkins
2.) You can now run jenkins by running the following command
sudo docker run -d --name=Jenkins -p 8080:8080 -p 50000:50000 -v jenkins-data:/var jenkins/jenkinsJust to explain the command above
run -d allows you to run the container in the background
--Name is just the name of the container you want to call this
-P lists the post you want to expose
-V creates a volume called -jenkins-data
At the end we reference the image name with is Jenkins
3.) To verify that Jenkins is up and running run the following
Docker PS
4.) In your local browser type in http://localhost:8080 which will advise you that it needs a password to unlock jenkins
5.) To retrieve this password to paste into your web browser type in the following:
sudo docker exec Jenkins cat /var/jenkins_home/secrets/initialAdminPassword
Copy the password in to the box seen previously in step 4
6.) This will bring you into a screen which will give you the option to install plugins> click on install suggested plugs
!Please note if you get an error with downloading the plugins please make sure you have used jenkins/jenkins rather than just jenkins for the repo (see step 1)
7.) It will then advise you to create your first admin user. Fill out the details required and click save and continue
8.) It'll then ask you if you want to customise your jenkins URL for now leave this on the default
9.) Welcome- you'll now see the Jenkins Dashboard!
And there we have it! We have jenkins installed. Watch this space as there will be another blog post up soon in regards to creating our very own jobs to run in Jenkins.
Yorumlar