Automatically build and deploy using Docker+Jenkins

This article introduces Docker+Jenkins automatic build deployment and shares it with you. The details are as follows:

environment

• Alibaba Cloud ESC, install Docker on the host server, and confirm that port 8080 is open in the security rules.
• Client Mac

Run Jenkins

Run the Jenkins container

Create a directory on the host and add read and write permissions so that the Jenkins application can read and write files when it runs, such as:

$ mkdir -p /var/jenkins_node
$ chmod 777 /var/jenkins_node

Pull the jenkins image: docker pull jenkins , the current version is 2.60.3 . And run:

docker run -d --name myjenkins -p 8080:8080 -p 50000:50000 -v <your_jenkins_path>:/var/jenkins_home jenkins

Mount the previous directory as a data volume. Replace <your_jenkins> with your directory name. The path needs to be an absolute path.
Wait for dozens of seconds and check the jenkins_node directory to confirm whether there are files generated by the Jenkins application.
Log in to http://you_host:8080 to view. Whether the Getting Started interface appears.

Set up account and SSH login

On the Getting Started interface, you will need the initial password Unlock Jenkins.
The password will be displayed in the output terminal. You can also find it in the jenkins_home of the container according to the page prompts.
So you can

docker logs myjenkins
# Or enter the container docker exec -t myjenkins /bin/bash

Once you have the password, enter it and install the suggested plugins.
After completion, follow the prompts to set up your login account.

Install Publish Over SSH plugin

Home page -> Click System Management -> Manage Plugins -> Optional Plugins -> Filter: ssh -> Select Publish Over SSH plugin and click Direct Installation.

Set server SSH information

First generate the RSA key in the container:

# Enter the container from the host client. The current container name is myjenkins. You can also view it through docker ps $ docker exec -it myjenkins /bin/bash
# After entering the container, create the .ssh directory and create the key files private key id_rsa and public key id_rsa.pub
~ mkdir ~/.ssh && cd ~/.ssh
~ ssh-keygen -t rsa
# Just keep pressing Enter

Add the public key to the host machine and add the string in id_rsa.pub to the end of the authorized_keys file. sudo service ssh restart restart
Note whether the ssh service is enabled on the host machine.
You can use the following command in the container terminal to add it to the host. You can also manually copy id_rsa.pub to the .ssh/authorized_keys file on the host machine.

ssh-copy-id -i ~/.ssh/id_rsa.pub <username>@<host>

You need to modify the ssh configuration file of the target server, the configuration file is /etc/ssh/sshd_config. Set ssh-server to allow login using private key and public key pair, and then restart the ssh service using the sudo /etc/init.d/ssh restart command.

Add Private Key
Jenkins homepage, System Management -> System Settings -> Scroll down and find Publish over SSH, fill in Key and SSH Server -> Save

Advanced options can configure ssh server port and timeout. Test can be tested, showing success configuration is successful.

Project Configuration

First, create a new task. Enter the project name.
Select source code management as: Git and fill in the URL of the project library. Private projects require adding a Git account.

Build environment: Select Send files or execute commands over SSH after the build runs , select the server, and add Exec command . save.

# Write according to your project needs sudo docker stop <node> || true \
  && sudo docker rm <node> || true \
  && cd /var/jenkins_node/workspace/<node> \
  && sudo docker build --rm --no-cache=true -t <node> - < Dockerfile \
  && sudo docker run -d --name <node> -p 3000:3000 -v 
  /var/jenkins_node/workspace/node:/home/project <node>

The port is set to 3000. You can also set -p 宿主機端口:容器端口separately. Remember to confirm whether the server port permission is enabled.

Dockerfile

# Write the FROM node according to your project needs
RUN mkdir -p /var/www/html/ 
RUN npm install -g yarn
WORKDIR /var/www/html
EXPOSE 3000
CMD ["npm","start"]

ps: npm install -g cnpm --registry=https://registry.npm.taobao.org

Return to the home page, select the project, and build it now. After success, you can view the project through http://you_host:3000 port.

Configure webhook

Configure webhook to automatically deploy and obtain API tonken: Home -> Users -> Select the current user -> Settings -> Click Show API Token...

Add token: Return to home page -> Project -> Configuration -> Build trigger -> Select "Trigger remote build" -> Paste "API Token" content into "Authentication token"
Log in to the code hosting platform, find your project, select Manage, select Webhook, add the URL in the format http://<you_host>:<port>/job/<object_name>/build?token=<API Token>

Setting up Jenkins security policy

Home -> System Management -> Configure Global Security ->
Authorization policy, check Allow anonymous read access .

At this point, the automated construction and deployment are completed. When you push the code, it will be automatically built and deployed.

Deployment Error Finding

There are no major issues with code push and webhook, and you won't go wrong if you follow the examples.
The errors in the container are problems with image building and image running, as well as problems with communication between containers.

• Image building: View the Jenkins homepage --> View the project --> Latest構建歷史--> View Console Output to view控制臺輸出. Here you can see which step went wrong. Generally, Sending build context to Docker daemon is a Jenkins command issue, and then a Dockerfile issue.
• Image running: If the Console shows that the image is built successfully (you can also view it in docker images ), but the image fails to run, or the container exits after running, if the code runs well locally, it is usually due to an error in the CMD startup command. Run the container in the foreground, docker run -it --name <container_name> <image_name> /bin/bash , enter the container and run CMD manually to check the log output. In addition, docker exec -t <container_name> /bin/bash can enter the running container and easily view the code; docker logs <container_name> displays the running log output.

This is the end of this article about using Docker+Jenkins to automatically build and deploy. For more information about Docker Jenkins automatic build and deployment, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope you will support 123WORDPRESS.COM in the future!