[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-05-31 Thread db...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Eyal Ben Moshe 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Assignee:
 
 yossis Eyal Ben Moshe 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-02-10 Thread nickolay.rumyant...@emc.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nickolay Rumyantsev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nickolay Rumyantsev 
 
 
 
 
 
 
 
 
 
 My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact. Also raised: https://www.jfrog.com/jira/browse/HAP-690   I couldn't find a workaround so this is blocking me at the moment.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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

[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-02-10 Thread nickolay.rumyant...@emc.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nickolay Rumyantsev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nickolay Rumyantsev 
 
 
 
 
 
 
 
 
 
 My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact.Also raised: https://www.jfrog.com/jira/browse/HAP-690I couldn't find a workaround so this is blocking me at the moment. * UPDATE: *  all works fine if I don't use "Deployment properties" option. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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,

[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-02-10 Thread nickolay.rumyant...@emc.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nickolay Rumyantsev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nickolay Rumyantsev 
 
 
 
 
 
 
 
 
 
 My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance.During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names!Publishing rules are the following (yes, there are version-named directories as the dest):{code:java}/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL{code}I also tried appending the filename to the each rule, and a trailing slash too but it didn't help.I found a stackoverflow question about the same issue but there is not much information: http://stackoverflow.com/questions/30633080/artifactory-creating-folders-instead-of-deploying-artifact.Also raised: https://www.jfrog.com/jira/browse/HAP-690I couldn't find a workaround so this is blocking me at the moment. UPDATE: all works fine if I don't use "Deployment properties" option. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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

[JIRA] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-02-10 Thread nickolay.rumyant...@emc.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nickolay Rumyantsev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nickolay Rumyantsev 
 
 
 

Environment:
 
 Jenkins 1.625.3Artifactory plugin 2.4.7  (2.2.4 too) Artifactory OSS (latest docker image: 29d2cd2e846a) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-02-10 Thread nickolay.rumyant...@emc.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nickolay Rumyantsev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nickolay Rumyantsev 
 
 
 

Priority:
 
 Blocker Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [artifactory-plugin] (JENKINS-32869) Artifactory plugin creates directories instead of uploading files

2016-02-09 Thread nickolay.rumyant...@emc.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nickolay Rumyantsev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32869 
 
 
 
  Artifactory plugin creates directories instead of uploading files  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 yossis 
 
 
 

Components:
 

 artifactory-plugin 
 
 
 

Created:
 

 10/Feb/16 2:28 AM 
 
 
 

Environment:
 

 Jenkins 1.625.3  Artifactory plugin 2.4.7 (2.2.4 too)  Artifactory OSS (latest docker image: 29d2cd2e846a) 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Nickolay Rumyantsev 
 
 
 
 
 
 
 
 
 
 
My job builds some tgz and rpms. I configured it to use Artifactory plugin as a Generic deployer to my test Artifactory instance. During the execution plugin reports in the log that it found the artifacts and deployed them successfully. But it ran too fast so I check the artifacts on the Artifactory page. There I saw that instead of files there were directories with the same names! Publishing rules are the following (yes, there are version-named directories as the dest): 

 

/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.COREOS.tgz=>com/foo/bar/coreos/1.5.0.0-155.COREOS
/jenkins/workspace/BuildJob/RPMS/x86_64/1.5.0.0-155.RHEL.rpm=>com/foo/bar/rhel7/1.5.0.0-155.RHEL
 

 
I also tried appending the