That's disappointing. I just tried it again on my install and it works just fine.
Try the ol' printenv command instead. They both work for me. Pete On May 31, 2013, at 2:00 PM, David Burson <[email protected]> wrote: > Hi Pete, > > When I run: comm -3 <(declare | sort) <(declare -f | sort) > from a terminal, it works fine, but when I run it from Jenkins' Execute shell > Command, I get: syntax error near unexpected token `(' > > I looked at the man page for comm and I'm still lost. Any ideas? > > Thanks, > David > > On Friday, May 24, 2013 4:13:27 PM UTC-4, David Burson wrote: > Hi, > > I've spent a couple days now trying to figure out why our build script runs > fine from the command line, but gets "execution error: An error of type > -10810 has occurred. (-10810)" when Jenkins runs it. The problem is a bit of > Applescript we run towards the end of our script. > > When I simply put this line in Jenkins' Execute shell Command box: > osascript -e 'tell application "Finder" to activate' > I get the same error: > execution error: An error of type -10810 has occurred. (-10810) > > How can I get Jenkins to run a bit of Applescript? > > Thanks, > David > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
