Gradle ssh (uploadarchive) upload is a big pit.

Antecedent

Need to put some of the project's common package to the private server (too lazy to build a nexus environment, anyway, there is not much), and then through the Maven HTTP download, the results with gradle ssh upload how all is a failure, tossing the most days, then thought to add --info parameters to try (not blame me Think of the late, the key is that ya in 83% when the death there, no hint, you know I was in full compliance with the official documents.

after the first pit

After adding the info parameter:gradle uploadArchives --info

The results found that the original dead there is waiting for you to enter Yes or no, because the first SSH operation will need to save the verification information, but this hint is completely gradle output information hidden, only add info or debug to see, this time directly enter Yes.

a second pit.

Then it doesn't have to be done.

Gradle the URL mentioned in the official documentation also needs to be noted:repository(url: "scp://repos.mycompany.com/releases")

Yes, that's the back /releases , this means starting from the root directory, if you throw it to a user like me, then you have to write the full path, and of course, if the port number is not the same, you can get rid of it:

scp://repos.mycompany.com:1234/home/userName/repos/releases

Get it done.

Gradle ssh (uploadarchive) upload is a big pit.