Shulou(Shulou.com)06/02 Report--

Above on the left is my personal Wechat, if you need further communication, please add good friends. On the right is my official account "Openstack Private Cloud". If you are interested, please follow us.

I have wanted to practice the so-called CI/CD continuous integrated development for a long time, mainly because it is not used in the work, and I am not particularly familiar with the field of development. now the infrastructure automation is to serve the upper applications, and the development department is also a master, and we also need to take care of it, .

Briefly introduce the concept of CI/CD, which literally means continuous integration / continuous deployment or delivery, as follows:

Continuous integration (Continuous Integration,CI): in a continuous integration environment, developers will submit code tests frequently (several times a day). They must pass the unit test before building. If one test case fails, the integration cannot continue. The purpose is to quickly find problems and fix them. Then the code is built, deployed, tested, and then feedback on the test results, and continue to perform this process.

Continuous deployment (Continuous Deployment,CD): continuous deployment is the flexibility to deploy the project to any environment, such as test environment, pre-production environment, production environment, for quality team or users to use, identify problems and feedback.

Continuous delivery (Continuous Delivery,CD): release the final product to the production environment for users to use.

The following figure is a simple diagram (from the Internet) of implementing CI/CD through git+docker register + Jenkins + docker.

As you can see, the logical relationship is very simple, that is, the developer uploads the development code to git, triggers the automatic code compilation of Jenkins and builds the image, and pushes the image to the docker repository, such as Harbor, and the test environment or production environment pulls the image deployment from the docker repository.

It's not much nonsense, and we start planning to do it.

The publishing process is as follows:

1. Development language: Java

two。 Project code version management: Git

3. Code compilation: Maven

4. Continuous Integration: Jenkins

5. Delivery: delivered in the form of a Docker image and submitted to the image repository

6. Deployment: Docker host creation container

The environmental planning is as follows:

Jenkins 192.168.1.46

Docker 192.168.1.45

Git/Registry 192.168.1.44

Operating system: CentOS7.2

Image name format:

Project name-module name: code version (tag)

Workflow:

1. The developer submits the code to the Git version repository

2.Jenkins manual / timed trigger project build

3.Jenkins pull replacement code, code compilation, package image, push to image repository

4.Jenkins creates a container on the Docker host and publishes

Deploy Git repository

Install Git on the 192.168.1.44 host as follows:

1. Install Git# yum install git-Y2. Create a Git user and set the password # useradd git# echo git | passwd-- stdin git 3. Create the warehouse su-gitmkdir solo.gitcd solo.gitgit-- bare init4. Access the created warehouse # git clone git@192.168.1.44:/home/git/solo.git

Upload the project to the Git warehouse

Find an open source JAVA blog project from Github as a demonstration. Pull substitution code # git clone https://github.com/b3log/solo.git add private warehouse address # cd solo/# git remote remove origin # git remote add origin git@192.168.1.44:/home/git/solo.git submit to private warehouse # git add. # git commit-m "all" # git push origin master

Install Docker and configure the Java environment in 192.168.1.45 as follows:

1. Install the dependency package # yum install-y yum-utils device-mapper-persistent-data lvm2 2. Add Docker package source: # yum-config-manager\-- add-repo\ https://download.docker.com/linux/centos/docker-ce.repo3. Install Docker CE# yum install docker-ce-Y4. Configure accelerator # curl-sSL https://get.daocloud.io/daotools/set_mirror.sh | sh-s http://bc437cce.m.daocloud.io5. Boot and boot # systemctl start docker# systemctl enable docker6. To install the Java and Maven environment, first download the jdk installation package jdk-8u192-linux-x64.tar.gz# tar zxf jdk-8u192-linux-x64.tar.gz# mv jdk1.8.0_192 / usr/local/jdk1.8# wget https://archive.apache.org/dist/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.tar.gz# tar zxf apache-maven-3.5.4-bin.tar from the oracle official website. .gz # mv apache-maven-3.5.4 / usr/local/maven3.5# vi / etc/profileMAVEN_HOME=/usr/local/maven3.5JAVA_HOME=/usr/local/jdk1.8 PATH=$PATH:$JAVA_HOME/bin:$MAVEN_HOME/binCLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar export JAVA_HOME PATH CLASSPATH# source / etc/profile7. To install git, you need to use git:yum install git-y when jenkins runs pipeline

Install Jenkins

Jenkins is an open source software project, is a continuous integration tool based on Java development, for code compilation, deployment, testing and other work.

Jenkins is also a cross-platform, supported by most major platforms, and is easy to install, so we install it here by deploying the war package.

Download address: https://jenkins.io/download

Install Jenkins on the 192.168.1.46 host, download the Tomcat binary package and put the war package under webapps:

Install the Java environment first # tar zxf jdk-8u192-linux-x64.tar.gz# mv jdk1.8.0_192 / usr/local/jdk1.8# vi / etc/profileJAVA_HOME=/usr/local/jdk1.8 PATH=$PATH:$JAVA_HOME/binCLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar export JAVA_HOME PATH CLASSPATH# source / etc/profile# wget http://mirrors.jenkins.io/war-stable/latest/jenkins.war# wget http://mirrors.shu.edu. Cn/apache/tomcat/tomcat-8/v8.5.37/bin/apache-tomcat-8.5.37.tar.gz# tar zxf apache-tomcat-8.5.37.tar.gz# mv apache-tomcat-8.5.37 / usr/local/tomcat-jenkins# rm / usr/local/tomcat-jenkins/webapps/*-rf# unzip jenkins.war-d / usr/local/tomcat-jenkins/webapps/ROOT# cd / usr/local/tomcat-jenkins/bin/#. / Startup.sh # tail-f.. / logs/catalina.out... Jenkins initial setup is required. An admin user has been created and a password generated.Please use the following password to proceed to installation:a832e00bc8c3484698f74862a3a2459aThis may also be found at: / root/.jenkins/secrets/initialAdminPassword...

Deployment successful, visit Jenkins: http://192.168.1.46:8080

Note that port 8080 is opened on the firewall:

Firewall-cmd-add-port=8080/tcp

Firewall-cmd-add-port=8080/tcp-permanent

Enter the password output from the log above: a832e00bc8c3484698f74862a3a2459a, or obtain it from the native / root/.jenkins/secrets/initialAdminPassword file, click continue, and select the recommended plug-in to install.

Wait for the plug-in to be installed later. Then create the first administrative user:

Account password admin. Next, configure jenkins:

Name: Slave node name

Number of concurrent builds: the maximum number of tasks sent to the Slave at the same time

Remote working directory: working directory on Slave

Tags: tags to identify which Slave

Usage: only responsible for the task of marking Job to the Slave

Startup method: Linux Slave generally uses SSH connection

Host: Slave IP address. This is Docker host IP.

Credentials: select the credentials you just created, and the username and password that SSH connects to the host.

Java path: java absolute path on Slave

After adding a new node, you need to connect to the docker node. When you connect for the first time, it is reported that ssh_hosts does not save the public key of this address. You need to log in to 192.168.1.45 directly using ssh in the background, as shown below:

[root@jenkins secrets] # ssh 192.168.1.45The authenticity of host '192.168.1.45 (192.168.1.45)' can't be established.ECDSA key fingerprint is 64:b6:7a:b9:9d:65:e2:57:3f:61:d8:dc:6c:cc:6a:78.Are you sure you want to continue connecting (yes/no)? YesWarning: Permanently added '192.168.1.45' (ECDSA) to the list of known hosts.root@192.168.1.45's password: Last login: Sat Feb 2 17:34:39 2019 from 192.168.1.22 [root@docker] #

After that, you can log in to the new node correctly, as follows:

Authorize Docker hosts to pull Git repositories without interaction

Create a key pair on Docker host 192.168.1.45:

# ssh-keygen # enter all the way # ssh-copy-id git@192.168.1.44 test interactive login free: # ssh git@192.168.1.44

Create a new task

Pipeline is a workflow framework running on Jenkins, which connects single or multiple tasks that used to run independently. The publishing process uses Groovy scripts to write the entire life cycle, and supports reading the script directly from the code base. This concept is the current best practice of CI/CD.

The Jenkinsfile content is as follows:

Node ("192.168.1.45") {/ / specify the Slave tag / / pull code stage ('Git Checkout') {checkout ([$class:' GitSCM', branches: [[name:'$Tag']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [] UserRemoteConfigs: [[url: 'git@192.168.1.44:/home/git/solo.git'])} / $Tag compiles stage (' Maven Build') {sh 'export JAVA_HOME=/usr/local/jdk1.8 / usr/local/maven3.5/bin/mvn clean package-Dmaven.test.skip=true''} / / the project is packaged into the mirror by referring to the tag// code entered interactively by the user Image and push to stage ('Build and Push Image') {sh' REPOSITORY=192.168.1.44/library/solo:$ {Tag} cat > > Dockerfile 1.0.0 [git@harbor solo] $

Release the test!

Automated build and deployment is successful. During the build process, you can directly view the console output in build Histroy, as follows:

The specific contents are as follows for reference:

Started by user administratorRunning in Durability level: MAX_ SURVIVABILITY [Pipeline] nodeRunning on docker in / var/jenkins_home/workspace/blog-solo [Pipeline] {[Pipeline] stage [Pipeline] {(Git Checkout) [Pipeline] checkoutNo credentials specifiedFetching changes from the remote Git repositoryChecking out Revision fca1bcbd6c4b3fe99625c68ae11d1166d06af556 (1.0.0) Commit message: "1" First time build. Skipping changelog. [Pipeline]} [Pipeline] / / stage [Pipeline] stage [Pipeline] {(Maven Build) [Pipeline] sh > git rev-parse-is-inside-work-tree # timeout=10 > git config remote.origin.url git@192.168.1.44:/home/git/solo.git # timeout=10Fetching upstream changes from git@192.168.1.44:/home/git/solo.git > git-version # timeout=10 > git fetch-tags-progress git@192.168. 1.44:/home/git/solo.git + refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/ 1.0.0 ^ {commit} # timeout=10 > git rev-parse 1.0.0 ^ {commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout-f fca1bcbd6c4b3fe99625c68ae11d1166d06af556 # timeout=10+ export JAVA_HOME=/usr/local/jdk1.8+ JAVA_HOME=/usr/local/jdk1.8+ / usr/local/maven3.5/bin/mvn clean package-Dmaven.test. Skip=true [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.b3log:solo:war:2.9.9 [WARNING] 'dependencies.dependency.systemPath' for org.patchca:patchca:jar should not point at files within the project directory {project.basedir} / src/main/resources/lib/net/pusuo/patchca-0.5.0.jar will be unresolvable by dependent projects @ line 245, column 25 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO]--

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.