Jenkins basic configuration

Take on the above .

1. Jenkins Basic configuration

1. take jdk and maven Copy to mount directory data in .

[[email protected] data]# pwd
/usr/local/docker/jenkins_docker/data
[[email protected] data]# ls
config.xml                      jdk                                             jobs              secret.key                users
copy_reference_file.log         jenkins.install.InstallUtil.lastExecVersion     maven             secret.key.not-so-secret  war
hudson.model.UpdateCenter.xml   jenkins.install.UpgradeWizard.state             nodeMonitors.xml  secrets                   workflow-libs
hudson.plugins.git.GitTool.xml  jenkins.model.JenkinsLocationConfiguration.xml  nodes             updates
identity.key.enc                jenkins.telemetry.Correlator.xml                plugins           userContent
[[email protected] data]# 

The purpose is to convert... Through data volumes jdk and maven Mapping to Jenkins Inside of container . Through the last article docker-compose.yml The document shows that , The mapped container internal path is /var/jenkins_home/.

2. Global tool configuration

• To configure jdk
• To configure maven

take setting.xml Configure to upload by yourself .

This step is to make Jenkins Can complete the compilation work .

3. The system configuration

• Publish Over SSH To configure

This step is to Bind target server . Run the compiled runnable package on the target server . You can select the key for connection , You can also use a password .

2. Process carding

Let's take a look at the picture drawn in the last article , The general process is summarized as ：

Developers submit code to GitLab（Gitee、Github All possible ）, adopt Git Parameter The plug-in implements from GitLab Warehouse pull code ,Jenkins Compile （ need jdk and maven）, And then use Publish Over SSH The plug-in connects to the target server to run , meanwhile , The target server has a containerized running environment .

thus , A basic set of process preparation work is completed .