cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Max Woghiren (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CB-6909) shellCmd and shellRunParam in master.cfg use values for master, fails on Windows slaves if OS X master
Date Mon, 21 Jul 2014 16:20:38 GMT

    [ https://issues.apache.org/jira/browse/CB-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068713#comment-14068713
] 

Max Woghiren edited comment on CB-6909 at 7/21/14 4:20 PM:
-----------------------------------------------------------

It turns out that the presence of `/bin/sh -c` is essential for commands that involve wildcards,
as you can read about in the third question here: http://trac.buildbot.net/wiki/FAQ.

That FAQ suggests specifying commands as a string rather than a list of strings.  Does this
work as a solution for you?


was (Author: max.woghiren):
It turns out that the presence of `/bin/sh -c` is essential for commands that involve wildcards,
as you can read about in the third question [here](http://trac.buildbot.net/wiki/FAQ).

That FAQ suggests specifying commands as a string rather than a list of strings.  Does this
work as a solution for you?

> shellCmd and shellRunParam in master.cfg use values for master, fails on Windows slaves
if OS X master
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CB-6909
>                 URL: https://issues.apache.org/jira/browse/CB-6909
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Medic, Windows 8, WP8
>         Environment: OS X master, buildbot 0.8.8, Windows Server 2012R2 slave, buildslave
0.8.8
>            Reporter: Vladimir Kotikov
>            Assignee: Max Woghiren
>              Labels: medic, windows8, wp8
>
> shellCmd and shellRunCmd are defined in master.cfg and used for a lot of the build tasks.
But the value depends on the OS of the master, so if you have a OS X master and Windows client
(or vice versa) a lot of steps will fail.
> {noformat}
> shellCmd="/bin/sh"
> shellRunParam="-c"
> if is_Windows :
>     shellCmd="cmd"
>     shellRunParam="/c"
> {noformat}
> For some steps, like in wp8 and windows8 sections, we know they'll always run on Windows
so we could always use 'cmd'. But in common sections or for a platform like android, it needs
to work on both.
> -----
> It seems that ShellCommand step already uses command interpreter according to slave platform
(see http://docs.buildbot.net/current/manual/cfg-buildsteps.html#step-ShellCommand). So it's
safe to remove this and specify commands for ShellCommand steps just with list of strings.
> Another possible issue is different path delimiter on windows and other platforms. But
in most cases slash instead of backslash works fine on windows. So it is possible to replace
'\\' to '/' in windows build steps.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message