Using Jenkins to build the publishing system

Goal

As the project deployed in the company intranet, each release code to be uploaded through the fortress machine, and then into the intranet download, and then RZ to the server, and finally unzip.
Each update is so repetitive that it is intended to deploy Jenkins as a publishing system on the Intranet machine. The following features are implemented:
1. Upload Code Compression Package
2. Extract to Fixed directory Jenkins installation

This is a lot of online tutorials, a bunch of search, recommended: http://www.liaoxuefeng.com/article/001463233913442cdb2d1bd1b1b42e3b0b29eb1ba736c5e000

Download Jenkins:
Run the following command to start the service:

Java-jar jenkins.war configuration Nginx

Jenkins is bound to 8080 ports, forwarded via Nginx: http://bookong.iteye.com/blog/1961823 Jenkins Configuration manual upload attachment

Google "Jenkins upload local Files" to find a large circle, have not met what I need, are said to install publish over SSH Plug-ins, this plug-in implementation is uploaded in the server, rather than I want to upload my local files, The final discovery is that there is a file parameter in the parameterized build process:

After saving, you can upload a selection:
automatically extract to fixed directory

Project configuration-"Build"-"Execute shell"

#-o Force Overwrite-d specified directory
unzip-o/home/jenkins/webpack.zip-d/data/

Note that it is recommended that you create a new Jenkins user to start the Jenkins service execute the shell command if you have sufficient permissions to have an automatic publishing system, the release code is easy to save time.