Today, I will continue to introduce you to the relevant knowledge of Linux operation and maintenance. The main content of this article is a detailed explanation of the principle of Jenkins continuous integration.
1. The process of updating the portal website in the traditional manual mode
The enterprise portal website is the presentation of the enterprise on the Internet. A major task of the operation and maintenance engineer is to update the enterprise portal website. In the traditional mode, to update the portal website, developers need to complete the corresponding code, and then the operation and maintenance personnel are responsible for deploying the code to the production environment. When the developer gets the developer's code, the usual portal website update (small-scale modification) process is as follows:
1. Access through the browser to find the URL of the update file (which can be pictures, H5, PHP, etc.).
2. Determine the IP address of the target server through the URL, and determine whether the IP address is a virtual IP address. If so, find the real IP address in the background, and finally determine the target server.
3. Determine the user name, password and other basic information of the target server by searching the server asset list.
4. Log in to the server, be familiar with the basic structure of the server, and determine the basic information such as the publishing software, configuration file, main directory, and whether to open the virtual host of the web site.
5. Determine the location of the update file.
6. Back up the original old files.
7. Replace the update file.
Second, the current mainstream update portal method
It can be seen that the traditional manual update process of the portal website is troublesome and complicated. Currently, in addition to the manual way of updating the portal website, there are the following four ways to update the portal website:
1. Update based on SHELL script, Rsync and other methods.
2. Batch update based on automation tools such as Ansible, puppet, and saltstack.
3. Update based on hudson (charged) automation platform tools.
4. Update based on Jenkins (open source free) automation platform tool.
3. Introduction to Jenkins
Jenkins is an open source software project. It is a continuous integration tool developed based on JAVA. It is used to monitor continuous and repetitive work. It aims to provide an open and easy-to-use software platform, so that software projects can be continuously integrated.
Jenkins can be published in mainstream web containers such as Tomcat, or it can run independently. Typically used in conjunction with version management control tools. Common version control tools include SVN, Git, etc. The combination of Jenkins and other software is based on plug-ins. Therefore, when we use Jenkins, in addition to installing Jenkins, we also need to install the plug-ins we need according to actual needs.
The official website of Jenkins is: https://www.jenkins.io/ , the page is as follows:
Original is not easy, please indicate the source: https://blog.csdn.net/weixin_40228200