amazon ssm agent - AWS Run Command act different than running on server locally -
i having problems running commands on ec2 instance bamboo server. have command generated run command in aws console. place command in script on bamboo server , run it:
aws ssm send-command --document-name "aws-runpowershellscript" --targets '{\"key\":\"tag:name\",\"values\":[\"auto-scaling-group\"]}' --parameters '{\"commands\":[\"$fileexe = \\\"c:\\\\program files (x86)\\\\nunit\\\\nunit.consolerunner.3.7.0\\\\tools\\\\nunit3-console.exe\\\\\\\"\",\"$testdll = \\\"c:\\\\testframework\\\\testframework\\\\tests\\\\bin\\\\debug\\\\tests.dll\\\"\",\"[system.diagnostics.process]::start($fileexe,$testdll)\"]}' --comment "run test ui testing" --timeout-seconds 600 --region us-east-1 it run tests. runs chrome.exe browser , chromedriver.exe background processes. throws nosuchwindowexception because there no browser showing up...
i can run same command in powershell on instance locally: (*note same command pasted run command console generate code mentioned above.)
$fileexe = "c:\program files (x86)\nunit\nunit.consolerunner.3.7.0\tools\nunit3-console.exe\" $testdll = "c:\testframework\testframework\tests\bin\debug\tests.dll" [system.diagnostics.process]::start($fileexe,$testdll) it works just fine. chromedriver.exe background process , chrome.exe (the browser) regular app works normal.
i believe problem how run command running test program.
what difference between run command (send-command) , running powershell commands locally? shouldn't same thing?
thank in advance!
Comments
Post a Comment