Jenkins installation Configuration Instance

Recently prepared to build a CI platform to simplify the relevant work, now the Jenkins installation and configuration records as follows, to wait for later check.
Environment used: System centos7/win7 Jenkins version 2.7.3 Web container tomcat7 JDK version 1.8 (new Jenkins requires 1.8 version)

To download the Jenkins War package, I use the latest version of Jenkins2.7.3, put it under the WebApp directory below the server, and start the Tomcat auto load run. The browser's local server address is then Jenkins installed.

After filling in the password, enter the installation interface, select the default installation, wait for the Jenkins installation to complete and then create the first administrator account. The appropriate configuration is required below.
Into the system Management-Admin plugin-Optional plugin selection plugin for installation, I installed the following plug-ins Maven Integration plugin This plugin provides the ability to build MAVEN tasks. Deploy to Container Plugin This plugin provides the ability to publish to a container such as Tomcat.

role-based Authorization Strategy This plugin provides rights management capabilities (view this article)

Before you make a task configuration, you need to set up the MAVEN path in the System management-system settings, the JDK version, the Git address, and so on to facilitate later use. Then start configuring a task:

Modify the Tomcat-users.xml configuration file under Tomcat and open the user for Jenkins to upload the application.

This tomcat account should not be opened on the official server, or it may cause the server to be hacked ...