Send build artifacts over SSH

[JENKINS] Archiving /var/lib/jenkins/workspace/dockerdeploy/webapp/pom.xml to com.example.maven-project/webapp/1.0-SNAPSHOT/webapp-1.0-SNAPSHOT.pom [JENKINS] Archiving /var/lib/jenkins/workspace/dockerdeploy/webapp/target/webapp.war to com.example.maven-project/webapp/1.0-SNAPSHOT/webapp-1.0-SNAPSHOT.war [JENKINS] Archiving /var/lib/jenkins/workspace/dockerdeploy/server/pom.xml to com.example.maven-project/server/1.0-SNAPSHOT/server-1.0-SNAPSHOT.pom [JENKINS] Archiving /var/lib/jenkins/workspace/dockerdeploy/server/target/server.jar to com.example.maven-project/server/1.0-SNAPSHOT/server-1.0-SNAPSHOT.jar [JENKINS] Archiving /var/lib/jenkins/workspace/dockerdeploy/pom.xml to com.example.maven-project/maven-project/1.0-SNAPSHOT/maven-project-1.0-SNAPSHOT.pom channel stopped

SSH: Connecting from host [ip-172-31-0-27.ap-south-1.compute.internal] SSH: Connecting with configuration [Dockerhost] …

SSH: EXEC: completed after 1,204 ms SSH: Disconnecting configuration [Dockerhost] … ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [125]] Build step ‘Send build artifacts over SSH’ changed build result to UNSTABLE Finished: UNSTABLE

Hi there,

A stack trace and error message from inside a build log is hard to remote debug. Try to always include these 3 things.

  1. what did you try? (Code samples, command lines, screenshots, videos, etc)
  2. what did happen? (Error messages, description, outputs, stuff)
  3. what did you expect to happen?

Otherwise, it’s hard for us to get into your context and you’ll have to have someone who is exactly knowledgeable come along.