Thanks for the reply - I have partially solved the issue - insomuch as its not causing me an issue anymore but cant explain it fully.
I have set artifactory up so my deploy user only has deploy permissions and not delete - this is so versioned artifacts cannot be redeployed by accident. For all my other repos this will result in a 403 (as expected) if a version number already exists for the artifact that is trying to be deployed. However, for this repo it will give a broken pipe. No idea why is acting differntly but at least I know what the issue is, was a bit of a red herring for me. May represent a bug with the plugin? I can see its using HttpClient which used to be super buggy....maybe okhttp would be better! -- View this message in context: http://forums.jfrog.org/Artifactory-Gradle-plugin-giving-broken-pipe-tp7580503p7580510.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
