Several Jenkins-based automated deployment methods

Through previous efforts, the automatic compilation process was promoted in more than 60 project teams through scripts, and then "automatic deployment" was required. In the past few days, we have also considered how to implement the automatic deployment. I can summarize the following:

1. shared directory. Use the script net use \ remote_machine_ip \ cmd_folder (only through the script, the premise is directory sharing, there is a certain security risk)

2. Temporary File Transfer Server. Generally, automatic compilation is implemented. There is a set of source code management servers (such as SVN or git servers). On the compilation server, the compiled files are uploaded to the temporary file server or source code management server, run the command (SVN export or other) on the server to be deployed to download the latest compiled file from the file server and complete the deployment.

3. Use plug-ins:

For Windows-based, consider the CIFS plug-in, see: https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+CIFS+Plugin (. NET deployment can use this program)

Tomcat-based plug-ins, see: https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin (recommended Java program to use this plug-in for deployment, support tomcat/JBoss/gishfish, etc., Java server support enough)

4. For a Linux system, you can consider rsync, rscp, and other scripts to complete. This requires a Shell Foundation.

 

For more information, thank you!

PS: If you have any questions about Jenkins, @ me. You can discuss them together.