You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 26, 2019. It is now read-only.
I try to change 8100 port to anything else over command-line in order to perform the parallel execution. I saw that it is possible to change port at FBConfigurationTests.
Is there any possible way to change port over command-line?
I tried below line to change port but it failed. xcodebuild -configuration WebDriverAgent USE_PORT 8200
+ (NSRange)bindingPortRange
{
// 'WebDriverAgent --port 8080' can be passed via the arguments to the process
if (self.bindingPortRangeFromArguments.location != NSNotFound) {
return self.bindingPortRangeFromArguments;
}
#
// Existence of USE_PORT in the environment implies the port range is managed by the launching process.
if (NSProcessInfo.processInfo.environment[@"USE_PORT"]) {
return NSMakeRange([NSProcessInfo.processInfo.environment[@"USE_PORT"] integerValue] , 1);
}
return NSMakeRange(DefaultStartingPort, DefaultPortRange);
}
The text was updated successfully, but these errors were encountered:
Thanks for your answer. So I understand that it possibly needs code implementation to change port over command line. If yes you can close this ticket. Probably , I am going to fork it and work on it.
@cyildirim You can already change port by passing either arg or env. Problem here is Xcode needs to pass them to WDA. You can definitely do this via scheme definition, I am not sure if xcodebuild supports it from command line
I try to change 8100 port to anything else over command-line in order to perform the parallel execution. I saw that it is possible to change port at
FBConfigurationTests
.Is there any possible way to change port over command-line?
I tried below line to change port but it failed.
xcodebuild -configuration WebDriverAgent USE_PORT 8200
The text was updated successfully, but these errors were encountered: