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

Improve logic for shell script completion

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: xshell-plugin
    • Labels:
      None
    • Environment:
      This issue applies to all platforms
    • Similar Issues:

      Description

      Currently you can specify a script to call by simply removing the extension and XShell will automatically add .cmd on Windows. Not sure why .sh is not getting added on Linux because it should be mostly the default extension for bash scripts.

      Also would it be possible to not only add the default extension but also check for alternatives? Batch files on Windows have a .cmd extension nowadays, and not sure what options exist on Linux. So would be great if the plugin could support multiple extensions, select the best match or fails when executing the shell if multiple matches exist which can't be resolved.

        Attachments

          Activity

          Hide
          whimboo Henrik Skupin added a comment -

          I think that we can close this one. It's working fine now on Windows even when the script has a .cmd extension. Also for Linux is safer to not have a .sh extension and simply use the basename.

          Show
          whimboo Henrik Skupin added a comment - I think that we can close this one. It's working fine now on Windows even when the script has a .cmd extension. Also for Linux is safer to not have a .sh extension and simply use the basename.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            whimboo Henrik Skupin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: