[
https://issues.jenkins-ci.org/browse/JENKINS-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Skupin resolved JENKINS-13244.
-------------------------------------
Resolution: Not A Defect
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.
> Improve logic for shell script completion
> -----------------------------------------
>
> Key: JENKINS-13244
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13244
> Project: Jenkins
> Issue Type: Bug
> Components: xshell
> Affects Versions: current
> Environment: This issue applies to all platforms
> Reporter: Henrik Skupin
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
