jenkinsci / publish-over-ftp-plugin

https://plugins.jenkins.io/publish-over-ftp/
21 stars 33 forks source link

[JENKINS-36079] Regression in v.1.12 #61

Closed jira-importer closed 6 years ago

jira-importer commented 8 years ago

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:

https://ci.dcache.org/job/dCache-master/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
USER ************
331 Password required for ************.
PASS ********
230 User dcache-build logged in
PWD
257 "/" is current directory
TYPE I
200 Type set to I
CWD /
250 CWD command succcessful. New CWD is
CWD rolling/2.17
250 CWD command succcessful. New CWD is
SYST
215 UNIX Type: L8 Version: FTPDoor
PASV
227 OK (131,169,191,209,89,159)
LIST -a
150 Ready to accept ASCII mode data connection
226 36 files

Here's the data channel, providing the response to the LIST command.

dcache-2.17.0.43e7ad0-1.noarch.rpm
dcache-2.17.0.7deb9f0-1.noarch.rpm
dcache-2.17.0.62fd200-1.noarch.rpm
dcache-2.17.0.13a009b-1.noarch.rpm
dcache-2.17.0.ff48c27-1.noarch.rpm
dcache-2.17.0.d790aa8-1.noarch.rpm
dcache-2.17.0.b9792c7-1.noarch.rpm
dcache-2.17.0.abdae03-1.noarch.rpm
dcache-2.17.0.887b4d3-1.noarch.rpm
dcache-2.17.0.61d13ef-1.noarch.rpm
dcache-2.17.0.0d2f9c0-1.noarch.rpm
dcache-2.17.0.459680d-1.noarch.rpm
dcache-2.17.0.b40b8bd-1.noarch.rpm
dcache-2.17.0.e5a0042-1.noarch.rpm
dcache-2.17.0.56fb782-1.noarch.rpm
dcache-2.17.0.586e62f-1.noarch.rpm
dcache-2.17.0.78ee625-1.noarch.rpm
dcache-2.17.0.73bb943-1.noarch.rpm
dcache-2.17.0.291dbb1-1.noarch.rpm
dcache-2.17.0.d154a5f-1.noarch.rpm
dcache-2.17.0.c93dc6c-1.noarch.rpm
dcache-2.17.0.070a543-1.noarch.rpm
dcache-2.17.0.7b770bc-1.noarch.rpm
dcache-2.17.0.159c422-1.noarch.rpm
dcache-2.17.0.b21b4b4-1.noarch.rpm
dcache-2.17.0.1dbfbe5-1.noarch.rpm
dcache-2.17.0.dd15a13-1.noarch.rpm
dcache-2.17.0.a8d9592-1.noarch.rpm
dcache-2.17.0.942cca1-1.noarch.rpm
dcache-2.17.0.5180b99-1.noarch.rpm
dcache-2.17.0.9830f2d-1.noarch.rpm
dcache-srmclient-2.16.0SNAPSHOT-1.noarch.rpm
dcache-srmclient-2.17.0SNAPSHOT-1.noarch.rpm
srm-client-2.16.0-SNAPSHOT.tar.gz
srm-client-2.17.0-SNAPSHOT.tar.gz
dcache-2.17.0.08ee55b-1.noarch.rpm


Originally reported by iepe1eet, imported from: Regression in v.1.12
  • assignee: slide_o_mix
  • status: Resolved
  • priority: Critical
  • resolution: Fixed
  • resolved: 2018-02-01T18:34:17+11:00
  • imported: 2022/01/10
jira-importer commented 6 years ago

slide_o_mix:

I think this is fixed via the updates done for using the feature check which will be in the next release (1.13)

jira-importer commented 6 years ago

slide_o_mix:

Fixed via update to use better list commands if available on the server.