Instructions for deploying projects to remote machines using the Publish Over SSH plugin in Jenkins

Publish Over SSH Plugin Usage

Before using Publish Over SSH, you need to create an SSH private key. Configure password-free login between machines. Assume that machine A, ip is 192.168.AA.AAA, machine B: 192.168.BB.BBB, machine A can log in to machine B without password, and machine B can log in to machine A without password. The production method is:

Enter machine A and execute:

cd ~
ssh-keygen -t rsa

The following command indicates that you can log in to the machine 192.168.BB.BBB through the machine 192.168.AA.AAA without a password

ssh-copy-id 192.168.BB.BBB 

The verification method is: execute ssh 192.168.BB.BBB on machine A, and then execute ifconfig to check the current IP. If you find that the machine's IP has become 192.168.BB.BBB, it means that the password-free login setting is successful.

Enter machine B and execute:

cd ~
ssh-keygen -t rsa
ssh-copy-id 192.168.AA.AAA

The verification method is: execute ssh 192.168.AA.AAA on machine B, and then execute ifconfig to check the current IP. If you find that the machine's IP has become 192.168.BB.BBB, it means that the password-free login setting is successful.

Configure Publish Over SSH in System Configuration

Go to Jenkins->System Management->System Settings and configure Publish over SSH

Parameter Description:

Passphrase: Password (key password, if you set it)
Path to key: the path to the key file (private key)
Key: Copy the private key into this box
Disable exec: Disable running commands Private configuration:
SSH Server Name: a name for the server (whatever you want)
Hostname: The host name or IP address to which you need to connect to SSH (IP is recommended)
Username: Username
Remote Directory: Remote Directory
Use password authentication, or use a different key: You can replace the public configuration (select and expand the public configuration, which is very extensible)
Advanced for private configuration:
Port: Port (default 22)
Timeout (ms): Timeout (milliseconds) The default value is acceptable.
Disable exec: Disable running commands
Test Configuration: Test connection

Configure SSH in the built project:

Before execution, you need to cooperate with the Execute shell configuration in Build–>Post Steps, execute the scp command, and remotely copy the project to be copied to the remote machine. The content in the Execute shell is as follows:

scp -r /root/.jenkins/workspace/youxuan_api_pre/qt360-web/target/youxuan_api [email protected]:/usr/local/jenkinsTempFolder/
export BUILD_ID=DONTKILLME

Click the built project -> Configure -> Post-build operations, select Send build artifacts over SSH, and configure as follows (Note: the Exec command below is a script executed on the remote machine):

The script content is as follows:

#!/bin/bash
echo "===================start deploy project========================="
ps -aux | grep /usr/local/tomcat/ | grep -v grep > tomcat_info.txt
sed 's/ / /g' tomcat_info.txt > tomcat_info1.txt
sed 's/ / /g' tomcat_info1.txt > tomcat_info.txt
sed 's/ / /g' tomcat_info.txt > tomcat_info1.txt 
cat tomcat_info1.txt | cut -d' ' -f 2 > tomcat_info.txt
for line in `cat tomcat_info.txt`
do
  kill -9 $line
done
cd /usr/local/tomcat/webapps
rm -rf youxuan_api*
mv /usr/local/jenkinsTempFolder/youxuan_api /usr/local/tomcat/webapps
/etc/init.d/tomcat start
sync
echo 3 > /proc/sys/vm/drop_caches
echo "===================deploy project success========================="

Parameter Description:

SSH Server Name: Choose a name you configured in the system settings
Transfer Set Source files: files to be uploaded (Note: relative to the path of the workspace. You can fill in multiple values ​​as shown in the following configuration. By default, they are separated by )
Remove prefix: Remove the directory (only the directories in Transfer Set Source files can be specified)
Remote directory: Remote directory (fill in according to your needs, because I am testing here, so I am lazy and did not fill it in. The system configuration will be inherited by default)
Exec command: Write the command you want to execute in it (the new version requires both Transfer Set Source files and Exec command to be filled in, you don’t have to fill in them. The old version allows you to fill in only one)
upscale:
Exclude files: Excluded files (useful when you transfer directories, use wildcards, for example: **/*.log, **/*.tmp,.git/)
Pattern separator: Separator (Configure the separator of Transfer Set Source files. If you change it here, the above content also needs to be changed)
No default excludes: Disable the default exclude rules (see the help for details)
Make empty dirs: This option changes the default behavior of the plugin. The default behavior is to match whether the file exists and create a directory to store it if it exists. Selecting this option will create a directory to store the file, even if it is an empty directory. (Personal understanding)
Flatten files: Upload only files, do not create directories (except remote directories)
Remote directory is a date format: The remote directory creates a folder with a date (the date format needs to be configured in the Remote directory). For the specific format, refer to the following table:
Remote directory Directories created
'qa-approved/'yyyyMMddHHmmss qa-approved/20101107154555
'builds/'yyyy/MM/dd/'build-${BUILD_NUMBER}' builds/2010/11/07/build-456 (if the build was number 456)
yyyy_MM/'build'-EEE-d-HHmmss 2010_11/build-Sun-7-154555
yyyy-MM-dd_HH-mm-ss 2010-11-07_15-45-55
Exec timeout (ms): The timeout for running the script (in milliseconds)
Exec in pty: simulate a terminal execution script
Add Transfer Set: Add a configuration

Summarize

The above is the full content of this article. I hope that the content of this article will have certain reference learning value for your study or work. Thank you for your support of 123WORDPRESS.COM. If you want to learn more about this, please check out the following links