In this tutorial, we'll use Jenkins, SonarQube, Docker, and AWS to create an automated CI/CD pipeline for your web application. Every time you push new code to your GitHub repository, this pipeline will automatically build, test, analyze, and deploy your project to your AWS EC2 instance.
GitHub account
Knowledge of EC2 instances and AWS account
Understanding SonarQube, Docker and Jenkins
Create three EC2 instances with a security group that allows all Internet traffic.
Install Jenkins, SonarQube and Docker on each EC2 instance.
Connect the Jenkins instance to SonarQube, Docker instances and yourself via SSH as well.
Make these SSH connections passwordless by generating ssh keys and saving their IDs.
Install the plugin - SSH2 Easy in Jenkins and configure the server.
Configure server groups and server sites for Jenkins, SonarQube and Docker.
Create a new Jenkins job and add a git link to your repository with the branch you want to build and deploy.
Add build steps in the pipeline configuration to copy code from the Jenkins workspace to SonarQube and a Docker instance for analysis and deployment.
If you are new to AWS, you can take a lookIt isto create your AWS account.
- Now on the AWS dashboard click on
"Start Virtual Machine"
- Dvaput click now
"Number of cases"field and type 3.
Call them temporarily"cases".
to chooseubuntu virtual machine.
- Clique
"Create a new key pair", and call it"Jenkins"and download it with RSA (key pair type) and .pem (private key pair type) format.
Now finally,click Start instance.
Now navigate to the Instances page and rename them to Jenkins, SonarQube and Docker.
Configuring a security group
Under security details, for example, click security groups and click "Edit Incoming Rules".
In general, there is only one rule for port 22 for SSH.
We need to add some more rules like:
Port 8080, for Jenkins
Port 3000, to expose our web app
Port 9000, for SonarQube
Set the source to "Anywhere-IPv4", ie. 0.0.0.0/0
Now click on Save Rules to save the changes.
Installing Jenkins on an EC2 instance
To install Jenkins on a Jenkins instance, you must first ssh to your instance from your terminal by selecting that instance and clicking connect.
Issue this command
chmod 400 Jenkins.pemin your downloads directory where you downloadedJenkins.pemto ensure your key is not publicly visible.
Now, in the SSH client, copy the ssh command and paste it in your terminal…
To install Jenkins, run the following commands in your terminal:
sudo apt updatesudo apt install openjdk-11-jrecurl -fsSL https://pkg.jenkins.io/debian-stable/jenkins.io-2023.key | sudo tee \ /usr/share/keyrings/jenkins-keyring.asc > /dev/nullanddeb [signed-by=/usr/share/keyrings/jenkins-keyring.asc] \ https://pkg.jenkins.io/debian-stable binary/ | sudo tee \ /etc/apt/sources.list.d/jenkins.list > /dev/nullsudo apt-get updatesudo apt-get instaliraj jenkinsYou can check the status of Jenkins with the following command
sudo systemctl status jenkins
Now copy Jenkins public IPv4 address, paste it in your browser and put port number 8080 after it in format e.g.
For example - 13.126.140.207:8080
You will see the page askingUnlock Jenkins,
To unlock jenkins, paste secret key in admin password, you can get it with following command:
sudo cat /var/lib/jenkins/secrets/initialAdminPassword
After unlocking Jenkins, click on"Install suggested plugins"and then provide basic details about"Create first admin user" page.and access the Jenkins dashboard after completing all the necessary steps.
Installing SonarQube on an EC2 instance
SonarQube isan automated, self-managed code review tool that systematically helps you deliver clean code. As a core element of our Sonar solution, SonarQube integrates with your existing workflow and detects issues in your code to help you perform continuous code inspections of your projects.
Repeat the process in a new terminal to ssh to your instance that we did during the Jenkins installation.
To install SonarQube on your instance, run the following command in your terminal:
sudo apt updatesudo apt install openjdk-17-jrewget https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-10.0.0.68432.zip
To extract the zip file, run the following command:
sudo apt install unzipunzip sonarqube-10.0.0.68432.zipNow change to the Linux directory to run the installation file:
CD/home/ubuntu/sonarqube-10.0.0.68432/bin/linux-x86-64./sonar.sh console#this will start SonarQube on port 9000Installing Docker on an EC2 instance
To install docker, you need to repeat the process you performed when installing Jenkins and SonarQube. You need to ssh into your instance through your terminal.
Now, to install Docker on your Docker instance, run the following commands listed below.
please updateadequatepackage indexing and package installation to allowadequateto use the repository over HTTPS:
sudo apt-get updatesudo apt-get install \ ca-certificates \ curl \ gnupgAdd the official Docker GPG key:
sudo install -m 0755 -d /etc/apt/keyringscurl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpgsudo chmod a+r /etc/apt/keyrings/docker.gpgUse the following command to configure the repository:
and\"deb [arc="$(dpkg --print-architecture)" signed by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \ "$(. /etc/os-release &&and "$VERSION_CODENAME")"stable"| \sudo tee /etc/apt/sources.list.d/docker.list > /dev/nullTo install the latest version, run:
sudo apt-get instalacija docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-pluginVerify that the Docker Engine installation was successful by running itHello WorldPhoto:
sudo docker run hello-worldNow we want to use docker services without the sudo command. So to do this we need to add this current "ubuntu" user to the docker group.
sudo usermod -aG docker ubuntunewgrp dockerNow you can use docker services without sudo command.
We need to configure SSH connection from Jenkins to Jenkins, Jenkins to SonarQube and Jenkins to Docker for further processing. Also, we need to facilitate these connections by generating the ssh key and saving their ids.
To do so, follow these commands:
sudo su#this will take you to the root environmentvi /etc/ssh/sshd_config#you need to edit and make some changes to the ssh config file for the ssh connection to succeedAfter inserting the sshd_config file,press "me"to gain edit access, make the following changes to your file.
To save these changes and exit,press ":wq!"
systemctl reiniciar sshd#this will restart sshd servicesExit#this will allow you to exit the root environmentNow you need to set a password for your authentication instance.
sudo free password
You must repeat the above procedure in all three cases.
After completing the above procedure in all three instances,connect to your Jenkins instance in your terminaland run the following command to set up a connection between Jenkins and Jenkins, SonarQube and Docker.
chave ssh#this will generate an ssh key to store our ssh ids from other instances to make them passwordless.Press A nurse for all fields.
Now this process below has to be repeated again for all three public IP addresses of Jenkins, SonarQube and Docker on the Jenkins instance only.
I'm showing this with Docker Public IP, but you need to do this with all three.
ssh 65.1.131.68#sshor sshor ssh This will ask for the password you set earlier.
After successful authentication, you will be able to login to your Jenkins instance for that specific instance whose public IP you entered above.
Now,output typeCheck out.
Now we have to make this connection passwordless because we don't want to keep typing the password over and over again.
ssh-copy-id ubuntu@65.1.131.68#this will save the above IP ID and make it secure so it doesn't ask for a password the next time you try ssh again.
This will prompt for a password, after which it will become passwordless. You can confirm it with the commandssh 65.1.131.68, you will see that this time he can login without asking for a password.
After repeating the above process with the two remaining public IP addresses of Jenkins and SonarQube, go to the AWS Instances dashboard in your browser.
Copy the SonarQube public IP and paste it in your browser and put port 9000 after it in the format
For example - 65.0.3.87:9000
Now login with username - admin and password - admin
After logging in and changing your password, you will be taken to the SonarQube dashboard.
Press this icon.
Name your project and specify the name of the branch you want to analyze.
Now we have many options to choose a continuous integration tool. Let's stick with Jenkins for now.
On the next page, we'll select GitHub for the DevOps platform.
Now it will ask for configuration. ClickContinueto step 3 and selectothersince we will be implementing our HTML application. Copy the code he provides and keep it safe as we will be using it later.
click incomplete this tutorialto save it, and after saving go toMy Accounts>Security>Generate Tokens
Now create a token to integrate with Jenkins.
Copy the token and keep it safe as we will use it later.
Now go to Jenkins control panel, paste Jenkins public IP address and put port 8080 behind it in such format
:8080
We need to install some plugins on Jenkins to configure SonarQube and Docker.
Scanner SonarQube
On the Jenkins dashboard, click the buttonManage Jenkins>>Manage Plugins>>Available Plugins
Now in the available plugins look forScanner SonarQubeeuSimple SSH2.
After selecting them, click on "Install without reboot".
Now we need to configure some plugins and servers, so that all three instances can connect.
On the Jenkins dashboard, clickManage Jenkins >> Global Tool Configurationand look forScanner SonarQubebelow it.
After clicking "Add SonarQube Scanner", give it an appropriate name and check furtherinstall automaticallyfor your installation and thenTo save.
NowManage Jenkins >> Configure System, to search forSonarQube ServersI click "Add SonarQube"
Name it accordingly, copy SonarQube public IP and paste it and put port 9000 behind it in the following formathttp://
Simple SSH2
On the Jenkins dashboard, click the buttonJenkins Management >> System Configuration,to search for "Server Group Center" and then click on "To add" pod, below "List of server groups"
Here we need to add two server groups, one for Jenkins and one for Docker. Name them Jenkins-Server and Docker-Server.
Change the username ofsourceto doubuntu,and provide the password for this which you set earlier in the terminal for ssh authentication.
apply and save, and come back here again to add server pages.
Now, search"Server List"pod, belowJenkins Management>>System Configuration>>Server Group CenterI click "To add"for a list of servers.
Here you also need to add two server locations, one for Jenkins and one for Docker.Give them an appropriate name and mention the Docker and Jenkins public IP addresses in their respective server groups.
Apply and save.We're done with plug-in management.
Finally, we'll build our CI-CD pipeline for our simple HTML project (Netflix Clone).
In the Jenkins dashboard,click in "Create a job".
Give it a name, select the type of pipeline you want to create, and click"ALL GOOD".
In the configuration setting, select"Git"forsource code management.Copy and paste the git link from the GitHub repository.
Specify the branch you want to create and deploy to.
For pipeline automation, i.e. automatically starting the build process when new changes are pushed to GitHub. This will create an automated pipeline between the developers and the Jenkins pipeline.
For that we need to check this build trigger -"GitHub merge trigger for GITScm polling"
Click apply and save.
Now go to your GitHub repository and clickSettings>>webhooksand then click on"Add webhook".
Provide the URL in the following formathttp://
Now under the Jenkins DashboardPipeline CI-CDclick in"Build Now"to start the build process.
If everything is working as it should, you will see your build success status.
Configuring the Pipeline for SonarQube
Under CI-CD pipeline, click"To set up", to search forconstruction stagesI click on"Add build step"and select"Scanner Sonar Qube".
Now paste the code inAnalysis propertiesfield, which you copied from the SonarQube we saved.
Log in and save, and go to Jenkins Control Panel>>Manage Plugins>>System Configurationand add a server authentication token for SonarQube by clicking on"To add", and selectionJenkins.
Change the type tosecret textand paste the token's secret key that we copied and saved earlier. Give it an appropriate ID name.
For nowserver authentication token, on the scroll bar select the name of the ID, the one you just created.
Now, in the CI-CD pipeline, click"Build Now".You will see success if all things work correctly.
Before clicking onbuild now, you must start SonarQube by running these commands in the SonarQube instance's terminal.
CD/home/ubuntu/sonarqube-10.0.0.68432/bin/linux-x86-64./sonar.sh console#this will start SonarQube on port 9000
Our pipeline now pulls users' code through GitHub and runs a build in Jenkins, which sends the code to SonarQube for code quality analysis.
Configuring Pipelines for Docker
We want to build a docker image of our application and then run it on port 3000 so that it is reachable and in a running state.
First ssh into your Docker instance via a terminal andcreate a folder page of the Internetto store the source code and build the Docker image.
site mkdirNow,inside the CI-CD pipelinein the Jenkins panel, click the button "to set up", to askconstruction stages,and selectremote shield.
We use Remote Shell because we want to run commands in Jenkins Docker.
The previous SSH connection we set up between Jenkins and Jenkins and Jenkins with Docker was just for that.
First, we direct the Jenkins server to copy the Jenkins workspace source code to the Docker server inside the website folder we just created.
CD/var/lib/jenkins/workspace/CI-CD-Pipeline/scp -r ./* ubuntu@65.1.131.68:~/web stranica/#this command safely copies all the code from the directory - CI-CD Pipeline and pastes it to the following destination - ubuntu@65.1.131.68:~/website/
Add another remote shell, this time to direct the Docker server to build and run the image.
CDweb stranica/docker build -t netflix .docker run -d -p 3000:3000 --name NETFLIX netflix
Apply and save.
If all goes well, you will see success. Here is our live website running on port 3000 on Docker.
Now you can also verify the pipeline by making some new changes in the GitHub repository, it will automatically start a new build process, analyze the code by uploading the code to SonarQube and the docker image will be rebuilt, reflecting the changes on port 3000 from to Docker instance.
This concludes our automated CI-CD pipeline here.
In this blog we learned how to build a CI/CD pipeline using AWS, Jenkins, SonarQube and Docker. It helps us automatically build, test, analyze and deploy our web applications. Cheers to us 🥳.
I've tried to make it very beginner friendly, but if you have any questions about it, feel free to DM me.
Don't forget to like and share this blog if you enjoyed it. Connect with me atTwitterfor updates on more of these blogs.
THANKS FOR READING!!😁✌️
FAQs
How do I make a CI CD pipeline in Jenkins and Docker? ›
- Jenkins-Docker Continuous Integration & Continuous Deployment Pipeline. ...
- chmod 400 /var/run/docker.sock. ...
- unix://var/run/docker.sock. ...
- Pipeline syntax-> select withcredentials from drop down -> secret text → select dockerHubaccount -> generate script. ...
- chmod 400 /var/run/docker.sock.
- Click on 'Create a job'.
- In the item name dialog box, you may enter the 'pipeline'.
- Select the pipeline job type in the list below.
- Click on OK.
Log into Jenkins as an administrator and go to Manage Jenkins > Configure System. Scroll down to the SonarQube configuration section, click Add SonarQube, and add the values you're prompted for. The server authentication token should be created as a Secret Text credential.
How do you pass sonar properties in Jenkins pipeline? ›Go to Manage Jenkins > Configure System and scroll down to the SonarQube servers section. This is where we'll add details of our SonarQube server so Jenkins can pass its details to our project's build when we run it. Click the Add SonarQube button. Now add a Name for the server, such as SonarQube.
How do I build a CI CD pipeline in AWS Devops? ›- Pull the source code from source control.
- Lint any configuration files.
- Run unit tests against the AWS Lambda functions in codebase.
- Deploy the test pipeline.
- Run end-to-end tests against the test pipeline.
- Clean up test state machine and test infrastructure.
- Send approval to approvers.
A CI/CD pipeline is a series of orchestrated steps with the ability to take source code all the way into production. The steps include building, packaging, testing, validating, verifying infrastructure, and deploying into all necessary environments.
What is pipeline code in Jenkins? ›Pipeline as Code describes a set of features that allow Jenkins users to define pipelined job processes with code, stored and versioned in a source repository.
What are the different ways to write a Jenkins pipeline? ›A Jenkinsfile can be written using two types of syntax - Declarative and Scripted. Declarative and Scripted Pipelines are constructed fundamentally differently. Declarative Pipeline is a more recent feature of Jenkins Pipeline which: provides richer syntactical features over Scripted Pipeline syntax, and.
What is Jenkins build process? ›A Jenkins build job contains the configuration for automating a specific task or step in the application building process. These tasks include gathering dependencies, compiling, archiving, or transforming code, and testing and deploying code in different environments.
How to pass Jenkins credentials to Docker? ›In Jenkins you have to add a new credential with your Docker Hub account details. Go to Credentials → Global → Add credentials and fill out the form with your username and password.
How to build Jenkins pipeline with parameters? ›
- Type: the data type for the parameter (string, boolean, etc.)
- Name: the name identifying the parameter.
- Default value: an optional value that will be used when a user doesn't specify one.
- Description: optional text that describes how the parameter is used.
AWS brings in a complete set of CI/CD developer tools to accelerate software development and release cycles. AWS CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the defined release model.
How do I create a build pipeline in AWS? ›- Step 1: Create and name your pipeline. Sign in to the AWS Management Console and open the CodePipeline console at http://console.aws.amazon.com/codesuite/codepipeline/home . ...
- Step 2: Create a source stage. ...
- Step 3: Create a build stage. ...
- Step 4: Create a deployment stage. ...
- Step 5: Review the pipeline.
- Let's Start Deploying. First, you need an account with AWS. ...
- Example Application. ...
- AWS Requirements. ...
- Staying Organized. ...
- The AWS Management Console. ...
- Create an IAM User. ...
- Create an S3 Bucket. ...
- Create your EC2 Instance.
The CI/CD pipeline combines continuous integration, delivery and deployment into four major phases: source, build, test and deploy.
What is CI CD pipeline steps? ›There are four stages of a CI/CD pipeline 1) Source Stage, 2) Build Stage, 3) Test Stage, 4) Deploy Stage. Important CI/CD tools are Jenkins, Bambo, and Circle CI. CI/CD pipeline can improve reliability. CI/CD pipeline makes IT team more attractive to developers.
What is a real time example of CI CD pipeline? ›CI/CD pipelines real-life example
Netflix and Facebook are the prime examples that have successfully implemented CI/CD pipelines to deliver software updates and features quickly and with high quality. Netflix uses a custom-built platform called Spinnaker to manage its CI/CD pipelines.
Different Types of Jenkins CI/CD Pipelines. Scripted Pipeline. Declarative Pipeline. The Concept of Stages in Jenkins Pipeline.
What are 3 important stages in pipeline in Jenkins? ›Stage: This block contains a series of steps in a pipeline. i.e., build, test, and deploy processes all come together in a stage. Generally, a stage block visualizes the Jenkins pipeline process.
How to create pipeline in Jenkins step by step with example? ›- Install the Docker Pipeline plugin through the Manage Jenkins > Plugins page.
- After installing the plugin, restart Jenkins so that the plugin is ready to use.
- Copy one of the examples below into your repository and name it Jenkinsfile.
- Click the New Item menu within Jenkins.
How can you setup CI CD for a project using AWS Lambda? ›
- Basic Requirements.
- Step 1: Setting Up the GitHub Repository.
- Step 2: Writing the Lambda Function.
- Step 3: Defining the Infrastructure with Terraform.
- Step 4: Writing the Workflow.
- Step 5: Running the Workflow.
Both AWS CodePipeline and GitHub Actions offer easy-to-use tools for creating a workflow to run your code through different steps in the CI/CD process. CodePipeline offers more features for visualizing your workflow, while GitHub Actions' visualizations are less detailed but easier to use.
How do you practice CI CD pipeline? ›- Commit early, commit often. ...
- Keep the builds green. ...
- Build only once. ...
- Streamline your tests. ...
- Clean your environments. ...
- Make it the only way to deploy to production. ...
- Monitor and measure your pipeline. ...
- Make it a team effort.
A CI/CD engineer is a highly skilled individual who can improve CI/CD tools integration and operations and can also help ensure end-to-end quality of the integration systems.
How many types of CI CD pipeline are there? ›Consequently, there are two types of CI/CD pipeline tools. Cloud-native CI/CD pipeline tools work with software deployed in containers and managed by container orchestrators like Kubernetes or Docker Swarm.
What is code pipeline in AWS? ›Q: What is AWS CodePipeline? AWS CodePipeline is a continuous delivery service that enables you to model, visualize, and automate the steps required to release your software.
What is the difference between Jenkins and Jenkins pipeline? ›1 Answer. The major difference between any Jenkins job and a Jenkins Pipeline Job is that the Pipeline Scripted job runs on the Jenkins master. This uses a lightweight executor which uses only some resources to translate in the master to atomic commands that execute or send to the agents.
What is the difference between Jenkins and code pipeline? ›CodePipeline is a continuous "deployment" tool, while Jenkins is more of a continuous "integration" tool. Continuous integration is a DevOps software development practice where developers regularly merge their code changes into a central repository, after which automated builds and tests are run.
How many pipelines can be created in Jenkins? ›1 Answer. There are two types of pipelines in Jenkins: Declarative. Scripted.
How many pipelines are available in Jenkins? ›Jenkins provides two different syntaxes for pipelines. When DevOps engineers write a Jenkins pipeline, they can choose between declarative and scripted. The differences between the two are both subtle and significant.
What are the 2 types of projects you can Utilise in Jenkins? ›
The list of job types available in Jenkins are: Freestyle Project. Maven Project. Pipeline.
How to build Jenkins on AWS? ›- On the Configure page, choose Add build step, and then choose Run build on AWS CodeBuild.
- Configure your build step. Provide values for Region, Credentials, and Project Name. Choose Use Jenkins source. Save the configuration and run a build from Jenkins.
Docker Swarm is more comprehensive and highly customizable, whereas Jenkins is customizable with the help of plugins. Kubernetes and Jenkins provide low fault tolerance unlike Docker. Docker is a container engine that can make and handle containers, whereas Jenkins is a CI/CD model that can build and test applications.
How do I manually build in Jenkins? ›- From the Jenkins dashboard, click the job name in the table.
- Click Build Review in the sidebar menu. Complete the form to specify the parameters for build.
- To trigger the build, click the Build button.
- Prerequisites. ...
- Getting started with the Jenkins Docker image. ...
- Adding additional software to the Jenkins server. ...
- Installing additional Jenkins plugins. ...
- Publishing the custom Docker image. ...
- Passing Java arguments. ...
- Passing Jenkins arguments. ...
- Backup the Docker volume.
- Getting Started with Jenkins.
- Installing Jenkins.
- Starting the Jenkins Docker Container.
- Unlocking Jenkins.
- Instance Configuration.
- Creating a New GitHub Repository.
- Add the GitHub Credentials to Jenkins.
- Add the Docker Hub Credentials to Jenkins.
- Open up a command prompt window and similar to the macOS and Linux instructions above do the following:
- Create a bridge network in Docker. docker network create jenkins. ...
- Run a docker:dind Docker image. ...
- Proceed to the Setup wizard.
The first time Jenkins starts, the configuration is created along with the administrator user and password. The default user credentials are admin and password .
How to create Jenkins pipeline using code? ›- Step 1: Go to Jenkins home and select “New Item”
- Step 2: Give a name, select “Pipeline” and click ok.
- Step 3: Scroll down to the Pipeline section, copy the whole pipeline code in the script section and save it.
- Step 4: Now, click “Build Now” and wait for the build to start.
- Create a WORKFLOW job.
- Enable "This build is parameterized".
- Add a STRING PARAMETER foo with default value bar text .
- Add the code below to Workflow Script : node() { print "DEBUG: parameter foo = ${env.foo}" }
- Run job.
How do I trigger Jenkins pipeline automatically? ›
- Create a pipeline .
- In the Configuration stage of your new pipeline, add a trigger .
- Select Jenkins from the Type menu, which brings up the following screen:
- Select a Jenkins master from the Master drop-down menu, then select a job from the Job drop-down.
- Build images.
- Run your image as a container.
- Use containers for development.
- Run tests.
- Configure CI/CD.
- Deploy your app.
If you run CI/CD with docker containers, you can call it CI/CD Docker. With the perfect application of the docker container or hub, you can improve the overall experience of CI/CD workflows without reaching its limit. The main focus of the CI/CD pipeline is to deliver and integrate changes continuously.
How to configure Jenkins with Docker? ›- Select the Manage Nodes and Clouds item in the System Configuration section.
- Click Configure Clouds in the menu on the left side.
- Expand the Add a new cloud list and select Docker.
- Provide the name and URI for the Docker host in the relevant fields.
- Clone the project from the AWS code samples repository.
- Deploy the AWS CloudFormation template to create the required services.
- Update the source code.
- Setup GitHub secrets.
- Integrate CodeDeploy with GitHub.
- Trigger the GitHub Action to build and deploy the code.
- Verify the deployment.
Docker enables the most powerful benefits of continuous integration and delivery: building and testing in isolation. Building CI/CD pipelines with Docker takes advantage of clean containers to eliminate any dependency issues that arise from local application development.
How does Jenkins CI CD pipeline work? ›Jenkins is an open-source automation tool for Continuous Integration (CI) and Continuous Deployment (CD). It is a server-based system that runs in servlet containers like Apache Tomcat.
Why Docker is used in Jenkins? ›Docker is a container engine that can create and manage containers, whereas Jenkins is a CI engine that can run build/test on your app. Docker is used to build and run multiple portable environments of your software stack. Jenkins is an automated software testing tool for your app.
Can Jenkins work without Docker? ›I know that jenkins can be installed without a docker at all (“Installing Jenkins - Linux”).
What is the command used to run Jenkins in a docker? ›| Command Section | Description |
|---|---|
| docker run | Tells docker to going to run a container image |
| --name jenkins | Names the container being launched jenkins . This is done for ease of referencing it later. |
| -v /var/run/docker.sock:/var/run/docker.sock | Mounts the local docker daemon socket to the Jenkins container. |
How to install and run Jenkins with Docker Compose? ›
- Step 1 – Create Atlantic.Net Cloud Server. ...
- Step 2 – Configure Repository. ...
- Step 3 – Install Docker. ...
- Step 4 – Create Docker Compose File for Jenkins. ...
- Step 5 – Start Jenkins Container. ...
- Step 6 – Access Jenkins Web UI.