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

1. Introduction of related concepts:

Continuous: constantly getting feedback, responding to feedback

Integration: compile, package, test

Deployment (Deployment): code or configuration changes to application components or infrastructure take effect in the production environment

Release: functional changes with business impact are visible to end users

Delivery: it can be understood as the phase from Deployment to Release, emphasizing the ability of developers to deploy frequently and the ability of business to release at any time.

Jenkins: an open source, extensible, Web-based continuous integration platform

Git: an open source distributed version control system

GitLab: an open source project for warehouse management systems, using Git as a code management tool, and a Web service built on this basis

Maven: a project management and automatic build tool based on the project object model (POM) for compiling source code and packaging

Nexus:Maven private server

SonarQube: an open source platform for code quality management and testing

Node.js: JavaScript runtime environment based on Chrome V8 engine

ZrLog: open source Java blog system (compiled, packaged and released as zrlog-2.1.3.war)

2. Preparation work (all 3 nodes need to perform the following operations):

1. Demo environment:

IP

Operating system

Hostnam

Deploy the package

192.168.1.144

CentOS 7.6 x86_64

Node1

JDK (jdk-8u221-linux-x64.tar.gz)

Node.js (node-v12.10.0-linux-x64.tar.xz)

Git (git-2.23.0.tar.xz)

Maven (apache-maven-3.6.2-bin.tar.gz)

Nexus (nexus-3.18.1-01-unix.tar.gz, port 8081, user name: admin, password: root@123)

Jenkins (2.176.3 installed in cognum mode, port 8080, user name: root, password: root@123)

192.168.1.145

CentOS 7.6 x86_64

Node2

GitLab (12.2.5 GitLab installation, port 8000, user name: root, password: root@123)

192.168.1.146

CentOS 7.6 x86_64

Node3

JDK (jdk-8u221-linux-x64.tar.gz)

Tomcat (apache-tomcat-8.5.45.tar.gz, port 8080, user name: root, password: root@123)

MySQL (5.7.27 MySQL installation, port 3306, user name: root, password: 123456)

SonarQube (sonarqube-7.7.zip, port 9000, user name: admin, password: root@123)

Demonstration goal: modify the source code of the local ZrLog project and submit it to GitLab through Git. If the code pushing the master branch will trigger Jenkins to build the project using Maven automatically, while the code pushing the dev branch will not trigger Jenkins to build the project using Maven, the code will be quality managed and tested through SonarQube after the project construction is completed, and finally released to the Tomcat of the remote node for automatic decompression and execution.

2. Close SELinux and firewalld

3. Configure epel source

4. Configure node time synchronization

5. Configure hostname

6. Configuration / etc/hosts file:

# vim / etc/hosts

192.168.1.144 node1

192.168.1.145 node2

192.168.1.146 node3

7. Download the required software packages:

(1) JDK: https://www.oracle.com/technetwork/java/javase/downloads/index.html

(2) Node.js: http://nodejs.cn/download/

(3) Git: https://mirrors.edge.kernel.org/pub/software/scm/git/

(4) Maven: http://maven.apache.org/download.cgi

(5) Nexus: https://www.sonatype.com/download-oss-sonatype

(6) Tomcat: http://tomcat.apache.org/

(7) SonarQube: https://www.sonarqube.org/downloads/

(8) ZrLog: https://github.com/*4fzb/zrlog

Note: due to the 51CTO forbidden words rule, please change the above * to 9 before you visit

Deploy the corresponding software packages on three and three nodes respectively:

1. Deploy JDK on node1 and node3 nodes respectively:

(1) decompress JDK:

# tar-xf jdk-8u221-linux-x64.tar.gz-C / usr/local

# cd / usr/local

# ln-sv jdk1.8.0_221 jdk

(2) configure JDK environment variables:

# vim / etc/profile.d/jdk.sh

Export JAVA_HOME=/usr/local/jdk

Export CLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar

Export PATH=$JAVA_HOME/bin:$PATH

#. / etc/profile.d/jdk.sh

# echo $JAVA_HOME

(3) View JDK version information: # java-version

2. Node1 node deploys Node.js:

(1) decompress Node.js:

# tar-xf node-v12.10.0-linux-x64.tar.xz-C / usr/local

# cd / usr/local

# ln-sv node-v12.10.0-linux-x64 node

(2) configure Node.js environment variables:

# vim / etc/profile.d/node.sh

Export NODE_HOME=/usr/local/node

Export PATH=$NODE_HOME/bin:$PATH

Export NODE_PATH=$NODE_HOME/lib/node_modules

#. / etc/profile.d/node.sh

# echo $NODE_HOME

(3) View Node.js version information: # node-v

Note: if you do not install Node.js, then when you build the ZrLog project, SonarQube Scanner will prompt "ERROR: Failed to get Node.js version. No CSS files will be analyzed."

3. Node1 node deploys Git:

(1) install dependent software packages:

# yum-y install gcc perl-ExtUtils-MakeMaker curl-devel expat-devel gettext-devel openssl-devel zlib-devel

(2) compile and install Git:

# tar-xf git-2.23.0.tar.xz-C / usr/src

# cd / usr/src/git-2.23.0

#. / configure-prefix=/usr/local/git-2.23.0

# make & & make install

# cd / usr/local

# ln-sv git-2.23.0 git

(3) configure Git environment variables:

# vim / etc/profile.d/git.sh

Export PATH=/usr/local/git/bin:$PATH

#. / etc/profile.d/git.sh

(4) View Git version information: # git-- version

Note: the version of Git installed by yum is 1.8.3, which is too low.

(5) create a local directory for storing ZrLog source code: # mkdir-pv / projects

(6) initialize the Git repository and clone the ZrLog source code:

# cd / projects

# git init

# git clone https://github.com/*4fzb/zrlog.git

Note: due to the 51CTO forbidden words rule, please change the above * to 9, and then clone the code.

# ls-a

# ls-a. Git

# ls-a zrlog

4. Node2 node deploys GitLab:

(1) create a yum repository of Tsinghua University's open source software image station with fast download speed:

# vim / etc/yum.repos.d/gitlab-ce.repo

[gitlab-ce]

Name=GitLab CE Repository

Baseurl= https://mirrors.tuna.tsinghua.edu.cn/gitlab-ce/yum/el$releasever/

Gpgcheck=0

Enabled=1

# yum clean all

# yum makecache

# yum repolist

(2) install GitLab:# yum-y install gitlab-ce

(3) modify the gitlab.rb configuration file:

# vim / etc/gitlab/gitlab.rb

Comment code: external_url 'http://gitlab.example.com'

New code: external_url 'http://192.168.1.145:8000'

New code: nginx ['listen_port'] = 8000

# gitlab-ctl reconfigure

# gitlab-ctl status

# systemctl status gitlab-runsvdir.service

# ps aux | grep gitlab

# ss-tunlp | grep 8000

Note: you can use # gitlab-ctl help to view the more detailed usage of the gitlab-ctl command

(4) configure GitLab to boot: # systemctl enable gitlab-runsvdir.service

(5) the browser accesses http://192.168.1.145:8000, enter the new password root@123, and click "Change your password":

Login: user name root, password root@123

(6) configure GitLab mail service:

# vim / etc/gitlab/gitlab.rb

Modify the following code:

Gitlab_rails ['smtp_enable'] = true

Gitlab_rails ['smtp_address'] = "smtp.qq.com"

Gitlab_rails ['smtp_port'] = 465

Gitlab_rails ['smtp_user_name'] = "834143808@qq.com"

Gitlab_rails ['smtp_password'] = "QQ Mail authorization code"

Gitlab_rails ['smtp_domain'] = "qq.com"

Gitlab_rails ['smtp_authentication'] = "login"

Gitlab_rails ['smtp_enable_starttls_auto'] = true

Gitlab_rails ['smtp_tls'] = true

New code: user ['git_user_email'] = "834143808@qq.com"

New code: gitlab_rails ['gitlab_email_from'] =' 834143808roomq.com'

# gitlab-ctl reconfigure

(7) Test whether the GitLab mail service is normal:

# gitlab-rails console

Irb (main): 001 Test','Hello GitLab' 0 > Notify.test_email ('834143808 bicycle qq.compose script GitLab Test','Hello GitLab'). Deliver_now

Remarks: Notify.test_email ('recipient email address', 'email title', 'email content') .deliver_now, enter, test and send

Receive email:

(8) enable the verification function of GitLab registered email:

Admin Area-- > Settings-- > General-- > Sign-up restrictions-- > Expand-- > check "Send confirmation email on sign-up"-- > Save changes

(9) configure GitLab username and mailbox:

Icon in the upper right corner-- > Settings-- > Profile-- > Full name (qiuyue)-- > Email (834143808@qq.com)-- > Update profile settings

To receive email, click "Confirm your email address":

Log in again:

Icon in the upper right corner-- > Settings-- > Profile-- > Public email (834143808@qq.com)-- > Update profile settings

Icon in the upper right corner-- > Settings-- > Emails-- > Delete the default mailbox admin@example.com

(10) enable allow requests from hooks and services to the local network:

Admin Area-- > Settings-- > Network-- > Outbound requests-- > Expand-- > check "Allow requests to the local network from web hooks and services"-- > Save changes

(11) create a GitLab project:

Fill in the project name zrlog,Visibility Level as "Private" and click "Create project":

Prompt "create SSH public key":

(12) create a SSH public key:

The node1 node generates a key pair:

# yum-y install openssh-clients

# ssh-keygen-t rsa-P ""

# ls-a ~ / .ssh

Copy the contents of the id_rsa.pub file

Icon in the upper right corner-- > Settings-- > SSH Keys-- > paste the contents of the id_rsa.pub file-- > Add key

Receive email:

The previous "create SSH public key" prompt has disappeared:

(13) the node1 node pushes the local zrlog project source code to the GitLab in the node2 node:

# git config-global user.name "qiuyue"

# git config-global user.email "834143808@qq.com"

# git config-global credential.helper store

# git config-global color.ui true

# git config-list

Note: the command # git config-- global credential.helper store is used to avoid entering a user name and password every time you enter a pull/push code

# cd / projects/zrlog

# git remote rename origin old-origin

# git remote add origin git@192.168.1.145:root/zrlog.git

# git push-u origin-- all

# git push-u origin-- tags

Note: the commands executed above can be found on the following page

Refresh this page and the warehouse of the zrlog project is no longer empty:

(14) create a dev branch and push the local zrlog project source code to the dev branch of GitLab in the node2 node:

# cd / projects/zrlog

# git branch

Note: default is master branch

# git branch dev

# git checkout dev

Note: create and switch to the dev branch

# git branch

Note: now defaults to dev branch

# git push-u origin dev

Refresh the page, which has become 2 branches:

(15) create "Access Tokens":

Icon in the upper right corner-- > Settings-- > Access Tokens-- > Name (zrlog)-- > Scopes (api)-- > Create personal access token

Access Tokens:nziSYx2sSMHmaDFs5x7Q

5. Node1 node deploys Maven:

(1) decompress Maven:

# tar-xf apache-maven-3.6.2-bin.tar.gz-C / usr/local

# cd / usr/local

# ln-sv apache-maven-3.6.2 maven

(2) configure Maven environment variables:

# vim / etc/profile.d/maven.sh

Export MAVEN_HOME=/usr/local/maven

Export PATH=$MAVEN_HOME/bin:$PATH

#. / etc/profile.d/maven.sh

# echo $MAVEN_HOME

(3) View Maven version information: # mvn-v

Note: the deployment of Maven depends on JDK

6. Node1 node deploys Nexus:

(1) create a Nexus installation directory: # mkdir-pv / usr/local/nexus

(2) decompress Nexus:

# tar-xf nexus-3.18.1-01-unix.tar.gz-C / usr/local/nexus

# cd / usr/local/nexus

Note: two directories will be generated after decompression, namely nexus-3.18.1-01 and sonatype-work

# ln-sv nexus-3.18.1-01 nexus

(3) modify the nexus-default.properties configuration file:

# vim / usr/local/nexus/nexus/etc/nexus-default.properties, modify the following code:

Application-host=0.0.0.0-- > application-host=192.168.1.144

Note: the default port number for Nexus listening is 8081.

(4) create a Nexus to start the user nexus, and grant the corresponding permissions:

# useradd nexus

# chown-R nexus.nexus / usr/local/nexus

(5) change the startup user of Nexus to nexus:

# vim / usr/local/nexus/nexus/bin/nexus.rc, modify the following code:

# run_as_user= "--> run_as_user=" nexus "

(6) start Nexus:

# ln-sv / usr/local/nexus/nexus/bin/nexus / usr/local/bin

# nexus start

Note: the parameter supported by nexus script is {start | stop | run | run-redirect | status | restart | force-reload}

# ps aux | grep nexus

# ss-tunlp | grep 8081

# tail-100 / usr/local/nexus/sonatype-work/nexus3/log/nexus.log

Note: if the nexus.rc file is not modified, you need to su-nexus before starting Nexus.

(7) when the browser accesses http://192.168.1.144:8081, click "Sign in" in the upper right corner:

Login: user name admin, default password is saved in / usr/local/nexus/sonatype-work/nexus3/admin.password file, here is b6873c5b-d8ee-4454-a17a-d99bc7f19f40

The new password is root@123

(8) modify the system file descriptor size and restart to take effect:

# ulimit-a

# vim / etc/security/limits.conf, with the following code added at the end:

* soft nofile 65536

* hard nofile 65536

# reboot

# ulimit-a

(9) start Nexus and refresh the page:

# nexus start

# ps aux | grep nexus

# ss-tunlp | grep 8081

(10) configure Nexus to boot:

# vim / etc/rc.d/rc.local

/ usr/local/nexus/nexus/bin/nexus start

# chmod + x / etc/rc.d/rc.local

Note: if the nexus.rc file is not modified, the boot command is su-nexus-c'/ usr/local/nexus/nexus/bin/nexus start'

(11) modify the address of maven-central warehouse in Nexus to Aliyun warehouse:

Click "maven-central", change the address https://repo1.maven.org/maven2/ in Remote storage to http://maven.aliyun.com/nexus/content/groups/public/, and click "Save":

Remarks: warehouse type

A, hosted: host warehouse for publishing internal projects, where maven-releases is used to store jar packages for releases versions, and maven-snapshots is used to store jar packages for snapshots versions.

B, proxy: agent warehouse, used to agent remote warehouse

C, group: warehouse group, which usually contains multiple host repositories and agent repositories, where maven-public is a collection of maven-central, maven-releases and maven-snapshots repositories

(12) modify the Deployment policy of maven-releases in Nexus to "Allow redeploy":

(13) node1 node modifies Maven configuration file:

# cd $MAVEN_HOME/conf

# cp settings.xml settings.xml.bak

# vim settings.xml

A. Configure the user name and password of the private server, and add the following code to the configuration section:

Nexus-releases

Admin

Root@123

Nexus-snapshots

Admin

Root@123

B. Configure the warehouse address and add the following code to the configuration section:

Nexus

Nexus

Http://192.168.1.144:8081/repository/maven-public/

True

True

Nexus

Http://192.168.1.144:8081/repository/maven-public/

True

True

Nexus

Note: the source of http://192.168.1.144:8081/repository/maven-public/ is shown in the following figure

(14) node1 node modifies common/pom.xml configuration file in ZrLog source code:

# vim / projects/zrlog/common/pom.xml, comment on the following code:

(15) node1 node modifies pom.xml configuration file in ZrLog source code:

# vim / projects/zrlog/pom.xml, add the following code to the configuration section:

Nexus-releases

Nexus Releases

Http://192.168.1.144:8081/repository/maven-releases/

Nexus-snapshots

Nexus Snapshots

Http://192.168.1.144:8081/repository/maven-snapshots/

Note:

A. The id here must be consistent with the id content under server in $MAVEN_HOME/conf/settings.xml.

B. The source of http://192.168.1.144:8081/repository/maven-releases/ is shown below.

C, the source of http://192.168.1.144:8081/repository/maven-snapshots/ is shown in the following figure

(16) the node1 node pushes the modification to the GitLab in the node2 node:

# cd / projects/zrlog

# git add.

# git status

# git commit-m "modify pom.xml"

# git push-u origin dev

# git status

Refresh the following page, and the content of the dev branch page has been updated:

Http://192.168.1.145:8000/root/zrlog/blob/dev/pom.xml

Http://192.168.1.145:8000/root/zrlog/blob/dev/common/pom.xml

The same goes for master branches:

# git checkout master

# git branch

# vim / projects/zrlog/common/pom.xml, as noted above

# vim / projects/zrlog/pom.xml, add the code in the configuration section as above

# git add.

# git status

# git commit-m "modify pom.xml"

# git push-u origin master

# git status

Refresh the following page, and the content of the master branch page has been updated:

Http://192.168.1.145:8000/root/zrlog/blob/master/pom.xml

Http://192.168.1.145:8000/root/zrlog/blob/master/common/pom.xml

(16) upload jar package to private server on node1 node:

The default warehouse is empty:

# cd / projects/zrlog

# mvn clean deploy-Dmaven.test.skip=true

Refresh the page http://192.168.1.144:8081/#browse/browse:maven-public

Refresh the page http://192.168.1.144:8081/#browse/browse:maven-releases

(17) node1 node downloads jar package from private server:

Find any dependency from https://mvnrepository.com/, such as https://mvnrepository.com/open-source/json-libraries

Click "Jackson Databind":

Select a version, such as 2.9.9.3:

Copy the code in the above red box to / projects/zrlog/pom.xml:

This jar package is not available locally before downloading from the private server: # find /-name jackson-databind-2.9.9.3.jar

# cd / projects/zrlog

# mvn clean deploy-Dmaven.test.skip=true

7. Node3 node deployment Tomcat:

(1) decompress Tomcat:

# tar-xf apache-tomcat-8.5.45.tar.gz-C / usr/local

# cd / usr/local

# ln-sv apache-tomcat-8.5.45 tomcat

(2) configure Tomcat environment variables:

# vim / etc/profile.d/tomcat.sh

Export CATALINA_HOME=/usr/local/tomcat

Export PATH=$CATALINA_HOME/bin:$PATH

#. / etc/profile.d/tomcat.sh

# echo $CATALINA_HOME

# catalina.sh version

(3) create a Tomcat to start the user tomcat, and grant the corresponding permissions:

# useradd tomcat

# chown-R tomcat.tomcat / usr/local/apache-tomcat-8.5.45

# chown-R tomcat.tomcat / usr/local/tomcat

(4) adjust the memory size used by JVM:

# vim / usr/local/tomcat/bin/catalina.sh

Add the code JAVA_OPTS='-server-Xms2048m-Xmx2048m' under the first line #! / bin/sh

Note: the memory size is adjusted according to the actual situation, and the server JVM had better set-Xms and-Xmx to the same value.

(5) configure Tomcat access:

# cd / usr/local/tomcat/conf

# cp tomcat-users.xml tomcat-users.xml.bak

# vim tomcat-users.xml, add the following code to the configuration section:

# vim / usr/local/tomcat/webapps/manager/META-INF/context.xml

Comment on the following code:

(6) start Tomcat:

# su-tomcat

$catalina.sh configtest

$catalina.sh start

$ps aux | grep java

$ss-tunlp | grep 8080

$tail-100 / usr/local/tomcat/logs/catalina.out

(7) browsers access http://192.168.1.146:8080

Click "Manager App" on the right, user name root, password root@123

(8) configure Tomcat to boot:

# vim / etc/rc.d/rc.local

Export JAVA_HOME=/usr/local/jdk

Su-tomcat-c'/ usr/local/tomcat/bin/startup.sh'

# chmod + x / etc/rc.d/rc.local

8. Node3 node deploys MySQL:

(1) remove the MySQL-related components built into CentOS 7.6:

# rpm-qa | grep-I mariadb--> mariadb-libs-5.5.60-1.el7_5.x86_64

# rpm-e-nodeps mariadb-libs-5.5.60-1.el7_5.x86_64

If you have previously installed MySQL, uninstall: # rpm-qa | grep-I mysql

If there is a / etc/my.cnf configuration file, delete: # rm-rf / etc/my.cnf first

(2) download mysql57-community-release-el7.rpm from http://repo.mysql.com/

(3) install mysql57-community-release-el7.rpm:# rpm-ivh mysql57-community-release-el7.rpm

Note: mysql-community-source.repo and mysql-community.repo will be generated in the / etc/yum.repos.d directory after installation

(4) install MySQL:

# yum-y install mysql-community-client mysql-community-libs mysql-community-common mysql-community-libs-compat mysql-community-devel mysql-community-server

(5) initialize MySQL:# mysqld-initialize-user=mysql-datadir=/var/lib/mysql

Note: make sure the / var/lib/mysql directory is empty before initialization

(6) modify / etc/my.cnf configuration file:

# mv / etc/my.cnf / etc/my.cnf.bak

# vim / etc/my.cnf

[mysqld]

Port=3306

Socket=/var/lib/mysql/mysql.sock

Datadir=/var/lib/mysql

Pid-file=/var/run/mysqld/mysqld.pid

Log-error=/var/log/mysqld.log

Lower_case_table_names=1

Character_set_server=utf8mb4

Collation_server=utf8mb4_general_ci

Innodb_file_per_table=1

Skip_name_resolve=1

Slow_query_log=1

Slow_query_log_file=mysql-slow.log

Symbolic-links=0

Explicit_defaults_for_timestamp=1

Server_id=1

Sync_binlog=1

Innodb_flush_log_at_trx_commit=1

Log_bin=mysql-bin

Log_bin_index=mysql-bin.index

Binlog_format=mixed

(7) start the MySQL service:

# systemctl start mysqld.service

# systemctl status mysqld.service

# ps aux | grep mysqld

# ss-tunlp | grep 3306

# tail-100 / var/log/mysqld.log

(8) configure MySQL service to boot: # systemctl enable mysqld.service

(9) check the initial password of the root@localhost user: # grep password / var/log/mysqld.log

(10) configure MySQL Security Wizard: # mysql_secure_installation

(11) create the databases and users required for ZrLog and SonarQube:

# mysql-uroot-p

Mysql > create database zrlog

Mysql > grant all on zrlog.* to 'zrlog'@'192.168.1.%' identified by' 123456'

Mysql > create database sonar default character set utf8

Mysql > grant all on sonar.* to 'sonar'@'192.168.1.%' identified by' 123456'

Mysql > flush privileges

Mysql > select user,host from mysql.user

(17) node1 node configures the MySQL database connection information in the ZrLog source code:

# cd / projects/zrlog

# git branch

# rm-rf web/src/main/webapp/WEB-INF/install.lock

# vim web/src/main/webapp/WEB-INF/db.properties

(18) the node1 node pushes the modification to the GitLab in the node2 node:

# cd / projects/zrlog

# git add.

# git status

Note: no code was pushed to GitLab when jackson-databind-2.9.9.3.jar was referenced in pom.xml.

# git commit-m "modify db.properties"

# git push-u origin master

Refresh the master branch page with updated content:

The same goes for dev branches:

# git checkout dev

# git branch

# rm-rf web/src/main/webapp/WEB-INF/install.lock

# vim web/src/main/webapp/WEB-INF/db.properties, modify the code as above

# git add.

# git status

# git commit-m "modify db.properties"

# git push-u origin dev

Refresh the dev branch page and the content has also been updated:

9. Node3 node deploys SonarQube:

(1) View the prerequisites for deploying SonarQube:

At present, the latest version is 7.9.1, and JDK 11 is required. MySQL is not supported.

Https://docs.sonarqube.org/7.9/requirements/requirements/

The version used here is 7.7, which is only compatible with JDK 8 and supports MySQL 5.6 or 5.7

Https://docs.sonarqube.org/7.7/requirements/requirements/

(2) modify the size of the system file descriptor and restart it to take effect:

# ulimit-a

# vim / etc/security/limits.conf, with the following code added at the end:

* soft nofile 65536

* hard nofile 65536

# reboot

# ulimit-a

(3) modify the system parameter value vm.max_map_count:

# vim / etc/sysctl.conf

Vm.max_map_count = 262144

# sysctl-p

(4) decompress SonarQube:

# yum-y install unzip

# unzip-qd / usr/local/ sonarqube-7.7.zip

# cd / usr/local

# ln-sv sonarqube-7.7 sonar

(5) configure SonarQube to access MySQL and Web related information:

# vim / usr/local/sonar/conf/sonar.properties, add the following code:

Sonar.jdbc.username=sonar

Sonar.jdbc.password=123456

Sonar.jdbc.url=jdbc:mysql://192.168.1.146:3306/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance&useSSL=false

Sonar.web.host=192.168.1.146

Sonar.web.context=/sonar

Sonar.web.port=9000

Note: database name is sonar

(6) create a SonarQube to start the user sonar, and grant the corresponding permissions:

# useradd sonar

# chown-R sonar.sonar / usr/local/sonarqube-7.7

# chown-R sonar.sonar / usr/local/sonar

(7) start SonarQube:

# ln-sv / usr/local/sonar/bin/linux-x86-64/sonar.sh / usr/local/bin

# su-sonar

$sonar.sh start

$sonar.sh status

$ps aux | grep sonar

$ss-tunlp | grep 9000

$tail-100 / usr/local/sonar/logs/sonar.log

Note: the parameter supported by sonar.sh script is {console | start | stop | restart | status | dump}

(8) when the browser accesses http://192.168.1.146:9000/sonar, click "Log in" in the upper right corner:

Login: both user name and password are admin

(9) modify the default password of admin users:

Click "Administrator"-> My Account in the upper right corner:

Click "Security":

Enter the old password as admin and the new password as root@123, and click "Change password":

(10) enable compulsory user authentication:

Click "Administration"-- > Configuration-- > Security-- > enable "Force user authentication"-> Save

(11) create a SonarQube project:

Project name: zrlog

Click "Generate" to generate Token:

Token:a8a629f19768a1cf81c4ed772f294c5a17eec854

The main language of the project: Java, the construction technology of the project: Maven

(12) the node1 node executes the code in the above red box in the project root directory (where the pom.xml is located) for code analysis:

# cd / projects/zrlog

Mvn sonar:sonar\

-Dsonar.projectKey=zrlog\

-Dsonar.host.url= http://192.168.1.146:9000/sonar\

-Dsonar.login=a8a629f19768a1cf81c4ed772f294c5a17eec854

(13) refresh the page to view the results of code analysis:

10. Node1 node deploys Jenkins:

(1) download Jenkins repository:

# yum-y install wget

# wget-O / etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo

# cat / etc/yum.repos.d/jenkins.repo

# rpm-- import https://pkg.jenkins.io/redhat-stable/jenkins.io.key

(2) download Jenkins:# yum-y install jenkins

Note: you can also download jenkins.war from https://jenkins.io/zh/download/, and then deploy the war package to launch under the webapps directory of Tomcat

(3) modify the startup script and make it effective:

# which java

# vim / etc/init.d/jenkins, add code under / usr/bin/java: / usr/local/jdk/bin/java

# systemctl daemon-reload

(4) start Jenkins:

# systemctl start jenkins.service

# systemctl status jenkins.service

# ps aux | grep jenkins

# ss-tunlp | grep 8080

Note: files and directories generated after installation

A, configuration file: / etc/sysconfig/jenkins

B. Listening port: 8080

C, war package location: / usr/lib/jenkins/jenkins.war

D. Cache directory: / var/cache/jenkins

E. Installation directory: / var/lib/jenkins

F, log file: / var/log/jenkins/jenkins.log

G. Startup user: jenkins

(5) configure Jenkins to boot: # systemctl enable jenkins.service

(6) browsers access http://192.168.1.144:8080

The default password is saved in the / var/lib/jenkins/secrets/initialAdminPassword file, where it is d81df2baa4e84f08b802a1baf3660232

Install the recommended plug-ins:

Login: user name root, password root@123

(7) Jenkins installs the specified plug-in:

Manage Jenkins-- > Manage Plugins-- > Available-- > install the Deploy to container Plugin, GitLab Plugin, Maven Integration plugin, NodeJS Plugin, Publish Over SSH, SonarQube Scanner for Jenkins plug-ins

Note: downloaded plug-ins are stored in the / var/lib/jenkins/plugins directory

# systemctl restart jenkins.service

Refresh the page:

Note: the interface language is automatically changed into simplified Chinese

(8) system Management-> Global Security configuration:

Check "allow users to register" and "Anonymous users have readable permissions":

Uncheck "prevent cross-site request forgery" and click "Save":

(9) system Management-> Global tool configuration:

Maven configuration:

JDK:

Git:

SonarQube Scanner:

Maven:

NodeJS:

Finally, click "Save"

(10) system Management-- > system Settings:

Maven project configuration:

Global attributes:

SonarQube servers:

Enter the Token:a8a629f19768a1cf81c4ed772f294c5a17eec854 of SonarQube at Secret

Gitlab:

Enter the Token:nziSYx2sSMHmaDFs5x7Q of GitLab at API token

Jenkins Location:

Git plugin:

Extended E-mail Notification:

The Extended E-mail Notification plug-in sends emails regardless of whether the project is built successfully or not, while the Mail Notification plug-in sends emails only when the project build is unstable or fails.

Publish over SSH:

The node1 node executes the following command:

# ssh-copy-id-I ~ / .ssh/id_rsa.pub root@192.168.1.146

# ssh root@192.168.1.146 'hostname'

Enter the private key content of ~ / .ssh/id_rsa in node1 at Key

Finally, click "Save"

4. Jenkins creates a new task:

General:

Source code management:

Enter the private key content of ~ / .ssh/id_rsa in node1 at git,Key for Username.

Build triggers:

GitLab webhook URL: http://192.168.1.144:8080/project/zrlog

Secret token:bb9547d853de09897f0d5ae8fff7c4c8

Configure GitLab webhook:

Build the environment:

Pre Steps remains the default

Build:

Post Steps:

Analysis properties:

Sonar.projectKey=zrlog

Sonar.projectName=zrlog

Sonar.projectVersion=1.0

Sonar.sources=./common/src,./data/src,./service/src,./web/src

Sonar.java.binaries=./common/target/classes,./data/target/classes,./service/target/classes,./web/target/classes

Sonar.language=java

Sonar.sourceEncoding=UTF-8

Sonar.login=admin

Sonar.password=root@123

Note: sonar.sources represents the directory where .java files are stored, and sonar.java.binaries represents the directory where .class files are stored. Different project files may be stored in different locations.

Build settings remain default

Post-build actions:

Editable Email Notification:

Deploy war/ear to a container:

Username and password configured in the conf/tomcat-users.xml file

Send build artifacts over SSH:

Exec command:

Su-tomcat-c "/ usr/local/tomcat/bin/shutdown.sh"

Sleep 5

Cd / usr/local/tomcat/webapps

Mv zrlog / tmp/zrlog_ `date +% Flying% T` & > / dev/null

Mv zrlog-*.war / tmp

Mv zrlog-* zrlog

Su-tomcat-c "/ usr/local/tomcat/bin/startup.sh"

Finally, click "Save"

5. Jenkins builds new tasks:

Build manually:

Click "build now":

Click "console output":

Deploy / var/lib/jenkins/workspace/zrlog/target/zrlog-2.1.3.war to the Tomcat of the remote node3 node for automatic decompression

Receive email:

View Nexus:

View SonarQube:

Install ZrLog:

Browsers access http://192.168.1.146:8080/zrlog

Administrator account: root, administrator password: root@123

"Click View" to display the home page:

Click "manage" to log in and display the background management:

ZrLog directory structure comparison:

Git source code directory:

Jenkins working directory:

Compile and package the released directory:

GitLab Test Webhook:

If the test is successful, return "HTTP 200":

Automatic build has been triggered:

Receive email:

View SonarQube:

The node1 node modifies the dev branch source code and pushes the GitLab to the node2 node. It does not trigger automatic construction:

# cd / projects/zrlog

# git checkout dev

# git branch

# echo "dev branch" > README.md

# git add.

# git commit-m "modify README.md"

# git push-u origin dev

The node1 node modifies the master branch source code and pushes the GitLab to the node2 node to trigger automatic construction:

# cd / projects/zrlog

# git checkout master

# git branch

# echo "master branch" > README.md

# git add.

# git commit-m "modify README.md"

# git push-u origin master

Receive email:

View SonarQube:

The final effect of all pages is as follows:

GitLab:

Nexus:

SonarQube:

Jenkins:

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.