驱动程序在 Jenkins 中不是可执行错误，而是在本地机器（MacBook）中运行

Question

我在 MacBook 上工作。 当我通过 testing.xml 文件运行测试时，我们的 Jenkins 服务器正在 linux 服务器中运行，所有测试类都在运行，但是当我运行 Jenkins 构建时，它没有运行错误是说驱动程序不可执行

我在 Jenkins 中创建了 maven 项目，并从 bitbucket 中给出了这个项目的 repo url

有人帮我解决这个问题吗？

    [INFO] Running TestSuite
java.lang.IllegalStateException: The driver is not executable: /var/lib/jenkins/workspace/TravelCenterSeleniumJenkinsIntegrationCMB/target/classes/chromedriver
    at com.google.common.base.Preconditions.checkState(Preconditions.java:585)
    at org.openqa.selenium.remote.service.DriverService.checkExecutable(DriverService.java:150)
    at org.openqa.selenium.remote.service.DriverService.findExecutable(DriverService.java:141)
    at org.openqa.selenium.chrome.ChromeDriverService.access$000(ChromeDriverService.java:35)
    at org.openqa.selenium.chrome.ChromeDriverService$Builder.findDefaultExecutable(ChromeDriverService.java:159)
    at org.openqa.selenium.remote.service.DriverService$Builder.build(DriverService.java:355)
    at org.openqa.selenium.chrome.ChromeDriverService.createDefaultService(ChromeDriverService.java:94)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:157)
    at utils.TestApp2.openBrowser(TestApp2.java:59)
    at uk.TravelcCenter_Tests.Sports_Shows_Tests.setUp(Sports_Shows_Tests.java:21)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
    at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:63)
    at org.testng.internal.ConfigInvoker.invokeConfigurationMethod(ConfigInvoker.java:348)
    at org.testng.internal.ConfigInvoker.invokeConfigurations(ConfigInvoker.java:302)
    at org.testng.internal.TestInvoker.runConfigMethods(TestInvoker.java:695)
    at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:523)
    at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
    at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
    at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
    at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
    at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
    at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
    at java.util.ArrayList.forEach(ArrayList.java:1259)
    at org.testng.TestRunner.privateRun(TestRunner.java:766)
    at org.testng.TestRunner.run(TestRunner.java:587)
    at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
    at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
    at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
    at org.testng.SuiteRunner.run(SuiteRunner.java:286)
    at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
    at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
    at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
    at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
    at org.testng.TestNG.runSuites(TestNG.java:1039)
    at org.testng.TestNG.run(TestNG.java:1007)
    at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:283)
    at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
    at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:120)
    at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
    at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

Answer 1

我的猜测 - 正是错误所说的，驱动程序不可执行。 SSH 到服务器，看看是否

sudo chmod 777 /var/lib/jenkins/workspace/TravelCenterSeleniumJenkinsIntegrationCMB/target/classes/chromedriver

修复它（777 分别为用户、组和其他人授予对文件的读/写/执行权限）。 如果您无法在任何条件下使用 SSH，您的 Jenkins 服务器可能需要在启动时使文件可执行

Answer 2

public static String osDetector() {
  String os = System.getProperty("os.name").toLowercase();
  if (os.contains("win") {
    return Windows;
  } else if(os.contains("nux") || os.contains("nix") {
    return Linux;
  } else {
    return "OtherOs";
  }
}

// under the openDriverMethod
ChromeOptions options = new ChromeOptions();
if (osDetector.contains("Windows") {
  System.setProperty("webdriver.chrome.driver", "driver folder path");
} else if(osDetector.contains("Linux") {
  System.setProperty("webdriver.chrome.driver", "driver folder path");
  //you need to add this one i guess!
  options.setBinary("/usr/bin/google-chrome");
}

Answer 3

我的项目中有 10 个测试类，其中 2 个类不是正确定义的 chrome 驱动程序实例，这就是我遇到上述问题的原因，现在对其进行了排序

Answer 4

就我而言，此解决方案对我有用。 你可以尝试一次

在这种情况下，当您安装 Jenkins 时，您为 Jenkins 创建了一个用户，现在您需要为 Jenkins 用户添加权限

这里有一些关于这个的很好的解释

https://medium.com/fusionqa/how-to-run-jenkins-using-the-root-user-in-linux-centos-79d96749ca5a#.pyshuihf0