Jenkins Advanced series--04publish over FTP plugin plugin

Description: This plugin can publish the build artifacts (for example, Jar) to FTP.

Official note: Publish over FTP Plugin

Installation steps:

System management → management plugin → optional plugin →artifact uploaders→publish over FTP Plugin

System Settings

FTP Server Name: Give yourself the name you want to see, what's it called?

Hostname: Host IP or domain name

USERNAME:FTP Login User Name

password:ftp Password

Remote directory: Remotely rooted directory (recommended setting:/)

Figure 1 System Setup Basic interface

Click Advanced on the test configuration above, such as:

Port: Ports (do not know to ask the administrator to go)

Timeout (ms): Time-out (ms)

Use Active Data mode: (unchecked) default option use PASV (passive mode), check using port (active mode)

Don ' t make nested dirs: Do not create sub-directories (see Help for yourself)

Figure 2 System Setup Advanced interface

There is also an advanced option in the lower right corner. Interested in themselves can be tossed down. Tip: You need to first save the page after the refresh, in the configuration. Otherwise there is an option that cannot be selected.

Project configuration

To enable the steps:

post-build actions → Add post-build action→send build artifacts over FTP

FTP Server Name: Select a configuration name that you configured in the system settings

Transfer Set Source files: file to be uploaded (note: The path to the workspace can be either a single file or a directory)

Remove prefix: Remove directory (only directories in transfer Set Source files can be specified)

Remote directory: (fill it out according to your needs, because I am testing here, so lazy to use directly/)

Figure 3 Project Setup Basic interface

Click Advanced on the back of remote directory, as

Exclude files: Excluded file (useful when you are transferring a directory, using wildcards, for example: **/*.log,**/*.tmp,.git/)

Pattern Separator: Delimiter (the delimiter that configures exclude files and source files. If you change here, the above content also needs to be changed)

No default excludes: the exclusion rule is forbidden (specific self-view help)

Make empty dirs: This option changes the default behavior of the plug-in. The default behavior is to match whether the file exists, and if so, create a directory store. Selecting this option creates a directory where the file is stored, even if it is an empty directory. (Personal understanding)

Flatten files: Create a file only on FTP, not directory (except remote directory)

Remote directory is a date format: a long-dated folder is created with a date format (you will need to configure the date formats in your rd directory), as described in 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

Clean remote: Deletes all files from the remote directory before uploading (the lesson of blood, the test is the operation of the team's FTP, and then accidentally deleted their data, harm I do data recovery.) ）

ASCII mode: The way the file is transferred, it is generally not selected by default.

Figure 4 Project Settings Advanced interface

Well, the usual options are these, the rest of their own toss it. This plugin is suitable for people who have a strong hands-on ability.

Pieces (Blood lessons ah, the test is the operation of the team's FTP, and then accidentally deleted their data, harm me to do data recovery.) ）

ASCII mode: The way the file is transferred, it is generally not selected by default.

Figure 4 Project Settings Advanced interface

Well, the usual options are these, the rest of their own toss it. This plugin is suitable for people who have a strong hands-on ability.

Jenkins Advanced series--04publish over FTP plugin plugin