[JIRA] (JENKINS-49518) Directory is not created anymore

2019-05-02 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49518  
 
 
  Directory is not created anymore   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49518) Directory is not created anymore

2018-02-26 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49518  
 
 
  Directory is not created anymore   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 Li-Wen Hsu Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49518) Directory is not created anymore

2018-02-12 Thread christof.dallerma...@43bits.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christof Dallermassl updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49518  
 
 
  Directory is not created anymore   
 

  
 
 
 
 

 
Change By: 
 Christof Dallermassl  
 

  
 
 
 
 

 
 After reinstallation of jenkins I ended up with version 1.13 of the publish-over-ftp plugin (not sure, which version I had before, probably 1.12). I did not change the jenkins config (ftp host) nor the jenkins tasks. Behaviour before update: The remote directory was created on the ftp serverBehaviour after: The remote directory is not created anymore and the file cannot be uploaded. Log of working jenkins task (before update of jenkins):{noformat}FTP: Connecting from host [2ea2fa14881a]FTP: Connecting with configuration [ftp.xxx.at] ...220 connected to ftp.xxx.at...FTP: Logging in, command printing disabledFTP: Logged in, command printing enabledCWD /foo/bar/Upload250 CWD command successful.TYPE I200 Type set to I.CWD /foo/bar/Upload250 CWD command successful.CWD db_dump_2018-02-03_1056550MKD db_dump_2018-02-03_1056257 "db_dump_2018-02-03_1056" directory created.CWD db_dump_2018-02-03_1056250 CWD command successful.PASV227 Entering Passive Mode (85,124,186,100,198,35).STOR backup_latest.pgdump125 Data connection already open; Transfer starting.226 Transfer complete.FTP: Disconnecting configuration [ftp.xxx.at] ...FTP: Transferred 1 file(s)Finished: SUCCESS{noformat}WIth the current plugin the log of the same jenkins task looks like:{noformat}FTP: Connecting from host [0dfc1108da61]FTP: Connecting with configuration [ftp.xxx.at] ...220 connected to ftp.xxx.at...FTP: Logging in, command printing disabledFTP: Logged in, command printing enabledCWD /foo/bar/Upload250 CWD command successful.TYPE I200 Type set to I.CWD /foo/bar/Upload250 CWD command successful.CWD db_dump_2018-02-10_1056FTP: Disconnecting configuration [ftp.xxx.at] ...ERROR: Exception when publishing, exception message [Exception when changing to FTP directory [db_dump_2018-02-10_1056]]Build step 'Send build artifacts over FTP' changed build result to UNSTABLE{noformat}What is missing is the{noformat}MKD db_dump_2018-02-03_1056{noformat}part now!My global ftp server config contains the base directory /foo/bar/UploadThe jenkins ftp upload task has the remote directory set to "'db_dump_'-MM-dd_hhmm" with the "Remote directory is a date format" checked in Advanced config.  Testing with manual ftp trying to find out if the server has changed its behaviour - "cd not_existing_directory" returned an error code 550, but did not close the ftp connection.  
 

  
 
 
 
 

 
 
 

[JIRA] (JENKINS-49518) Directory is not created anymore

2018-02-12 Thread christof.dallerma...@43bits.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christof Dallermassl created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49518  
 
 
  Directory is not created anymore   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Li-Wen Hsu  
 
 
Components: 
 publish-over-ftp-plugin  
 
 
Created: 
 2018-02-12 21:26  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Christof Dallermassl  
 

  
 
 
 
 

 
 After reinstallation of jenkins I ended up with version 1.13 of the publish-over-ftp plugin (not sure, which version I had before, probably 1.12). I did not change the jenkins config (ftp host) nor the jenkins tasks.  Behaviour before update: The remote directory was created on the ftp server Behaviour after: The remote directory is not created anymore and the file cannot be uploaded.   Log of working jenkins task (before update of jenkin
 s): 

 
FTP: Connecting from host [2ea2fa14881a]
FTP: Connecting with configuration [ftp.xxx.at] ...
220 connected to ftp.xxx.at...
FTP: Logging in, command printing disabled
FTP: Logged in, command printing enabled
CWD /foo/bar/Upload
250 CWD command successful.
TYPE I
200 Type set to I.
CWD /foo/bar/Upload
250 CWD command successful.
CWD db_dump_2018-02-03_1056
550
MKD db_dump_2018-02-03_1056
257 "db_dump_2018-02-03_1056" directory created.
CWD db_dump_2018-02-03_1056
250 CWD command successful.
PASV
227 Entering Passive Mode (85,124,186,100,198,35).
STOR backup_latest.pgdump
125 Data connection already open; Transfer starting.
226 Transfer complete.
FTP: Disconnecting configuration [ftp.xxx.at] ...
FTP: Transferred 1 file(s)
Finished: SUCCESS 

 WIth the current plugin the log of the same jenkins task looks like: