Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18172

Release on SSH slave broken (svn not found)

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We want to use 'ssh-slave' capabilities.
      During tests, we've made a release and an error occurred :

      ...
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 4.850s
      [INFO] Finished at: Mon Jun 03 10:34:06 CEST 2013
      [INFO] Final Memory: 10M/24M
      [INFO] ------------------------------------------------------------------------
      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project myjob: Unable to check for local modifications
      [ERROR] Provider message:
      [ERROR] The svn command failed.
      [ERROR] Command output:
      [ERROR] /bin/sh: svn: not found
      [ERROR] -> [Help 1]
      [ERROR]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR]
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

      The main build is a maven type build and works well if I launch a classic build.
      If I rollback to JNLP strategy to connect slaves, the release is OK.

      Thanks

        Attachments

          Activity

            People

            Assignee:
            petehayes Peter Hayes
            Reporter:
            mpapo Michael Pailloncy
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: