Status: Closed (View Workflow)
Since upgrading to v1.12, Publish-over-FTP does not work.
Reverting the plugin back to v1.11 has provided a temporary solution.
With v1.12, uploads fail with the following messages:
FTP: Connecting from host [sisyphus.desy.de]
FTP: Connecting with configuration [DESY dCache] ...
FTP: Disconnecting configuration [DESY dCache] ...
ERROR: Exception when publishing, exception message [Failed to parse a file entry returned from the server]
Build step 'Send build artifacts over FTP' changed build result to UNSTABLE
For an example of this, see the console output from build 6951:
I captured the network traffic between the FTP server and the Publish-over-FTP plugin using tcpdump.
Here are the TCP streams between the FTP client to the server.
First, here's the command-channel, obviously those starting with a number are replies from the server (I've replaced the username and password with stars):
220 Weak FTP door ready
331 Password required for ************.
230 User dcache-build logged in
257 "/" is current directory
200 Type set to I
250 CWD command succcessful. New CWD is </>
250 CWD command succcessful. New CWD is </rolling/2.17>
215 UNIX Type: L8 Version: FTPDoor
227 OK (131,169,191,209,89,159)
150 Ready to accept ASCII mode data connection
226 36 files
Here's the data channel, providing the response to the LIST command.
Fixed via update to use better list commands if available on the server.
For your information, all publish-over-ftp component type JENKINS issues related to the Publish Over FTP plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ftp-plugin/issues
Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ftp-plugin/issues/61
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ftp-plugin/issues?q=%22JENKINS-36079%22
(Note: this is an automated bulk comment)
This Resolved Issue has now been Closed. If you wish to follow up please see the Corresponding Github Issue
I think this is fixed via the updates done for using the feature check which will be in the next release (1.13)