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

Workflow support for XShell plugin

XMLWordPrintable

      It'd be nice to expose the xshell plugin functionality through as a workflow step.

      Came from this thread

          [JENKINS-26169] Workflow support for XShell plugin

          Kohsuke Kawaguchi created issue -
          Jesse Glick made changes -
          Component/s Original: workflow-plugin [ 18820 ]
          Assignee Original: Jesse Glick [ jglick ]
          Labels New: workflow
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Summary Original: workflow support for XShell plugin New: Workflow support for XShell plugin

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Jesse Glick
          Path:
          COMPATIBILITY.md
          http://jenkins-ci.org/commit/workflow-plugin/70cdf15d8a961fadb4c92c041675c7956a89496f
          Log:
          JENKINS-26169 Fixed formatting in note.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/70cdf15d8a961fadb4c92c041675c7956a89496f Log: JENKINS-26169 Fixed formatting in note.
          Jesse Glick made changes -
          Link New: This issue depends on JENKINS-26055 [ JENKINS-26055 ]
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-30372 [ JENKINS-30372 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-31691 [ JENKINS-31691 ]

          Colin Bennett added a comment -

          This would be great. It regrettable that making portable builds is so difficult. Here is a workaround in the meantime:

          #!groovy

node {
    execute 'cmake -G Ninja ..'
    execute 'cmake --build .'
    // Run a program that is in the current directory.
    executeCwd 'myprogram --test'
}

/**
 * Execute a program that exists in the current working directory.
 *
 * On Unix, the current working directory is not implicitly in the PATH,
 * so the command must be prefixed with "./".
 *
 * On Windows, the current directory is first in the search path, but
 * it does not like the "./" used for a Unix-style command.
 *
 * Therefore we have to do something special in each case.
 */
def executeCwd(commandString) {
    if (isUnix()) {
        execute("./" + commandString)
    } else {
        execute(".\\" + commandString)
    }
}

          Colin Bennett added a comment - This would be great. It regrettable that making portable builds is so difficult. Here is a workaround in the meantime: #!groovy node { execute 'cmake -G Ninja ..' execute 'cmake --build .' // Run a program that is in the current directory. executeCwd 'myprogram --test' } /** * Execute a program that exists in the current working directory. * * On Unix, the current working directory is not implicitly in the PATH, * so the command must be prefixed with "./" . * * On Windows, the current directory is first in the search path, but * it does not like the "./" used for a Unix-style command. * * Therefore we have to do something special in each case . */ def executeCwd(commandString) { if (isUnix()) { execute( "./" + commandString) } else { execute( ".\\" + commandString) } }
          Patrick Wolf made changes -
          Epic Link New: JENKINS-34657 [ 170293 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 160160 ] New: JNJira + In-Review [ 180276 ]
          Andrew Bayer made changes -
          Labels Original: workflow New: pipeline workflow

            Unassigned Unassigned
            kohsuke Kohsuke Kawaguchi
            Votes:
            9 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: