Open jtwile2 opened 6 years ago
Thanks for reporting this @jtwile2. We're looking into this and we'll update soon.
@jtwile2, We fixed this issue. Here is a link to the commit: https://github.com/JFrogDev/build-info/commit/2507ad7e1b5bcd5f38fc139096f98f8f8b107f75
Here is a snapshot which resolve this issue: https://oss.jfrog.org/oss-snapshot-local/org/jfrog/bamboo/bamboo-artifactory-plugin/2.4.x-SNAPSHOT/bamboo-artifactory-plugin-2.4.x-20180214.160028-5.jar
We'll appreciate you feedback for that!
@jtwile2, following my last message, please notice that the snapshot is compatible with bamboo 6.2.5 and above.
@yahavi This is working as expected, thankyou. Files with plus signs and files with spaces in the filename are deployed correctly. When is the next release of the plugin expected? I would prefer to run production with a released version instead of the snapshot.
@jtwile2, Thanks for your feedback! The next Bamboo plugin is planned to be released in the next few weeks.
This same issue also happens with Jenkins Artifactory plugin (v2.14). I wonder if there has already been a fix for it. Thank you.
Hello @bb-tle, The latest release of Jenkins Artifactory plugin (v2.15) contains the fix.
Thank you @yahavi v2.15 fixed the problem.
Hello @bb-tle, we are running Artifactory Version 6.5.13. When uploading helm chart with '+' sign in its name the uploaded artifact got ' ' (space ) instead of '+'. $ ls file-parser-5.5.1+* file-parser-5.5.1+1.tgz file-parser-5.5.1+2.tgz $ On Artifactory: $ curl -X GET https://++++++++++443/artifactory/api/storage/va-helm/file-parser { "repo" : "va-helm", "path" : "/file-parser", "created" : "2019-07-21T14:12:03.550Z", "createdBy" : "k8s", "lastModified" : "2019-07-21T14:12:03.550Z", "modifiedBy" : "k8s", "lastUpdated" : "2019-07-21T14:12:03.550Z", "children" : [ { "uri" : "/file-parser-5.5.0.tgz", "folder" : false }, { "uri" : "/file-parser-5.5.1 1-space.tgz", "folder" : false }, { "uri" : "/file-parser-5.5.1 1.tgz", "folder" : false }, { "uri" : "/file-parser-5.5.1 2.tgz", "folder" : false }, { "uri" : "/file-parser-5.5.1-1.tgz", "folder" : false }, { "uri" : "/file-parser-5.5.1-2.tgz", "folder" : false }, { "uri" : "/file-parser-5.5.VERTHREE-13406-SNAPSHOT.tgz", "folder" : false } ], "uri" : "https://++++++:443/artifactory/api/storage/va-helm/file-parser" $
Note, that helm chart should use Sem Ver 2 for version where '+' separates release and build number. https://semver.org/ https://helm.sh/docs/developing_charts/
Could you check please if this is a bug? regards, Dmitry
@karapuz50, Is your question related to the Bamboo Artifactory Plugin? If so, can you please be more specific on how you upload the helm chart using Bamboo?
@eyalbe4 No, it's not related to any plugin. I've uploaded the artifacts via UI.
Using v2.4.1 of the plugin:
When using either legacy patterns or File Specs, if a filename found by the discovery pattern has spaces in the filename, those spaces are replaces with plus signs. Log below:
I would expect the artifact to be uploaded as 'File with spaces.pkg' instead of 'File+with+spaces.pkg'
Thanks