Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31305

SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • sauce-ondemand-plugin
    • None
    • Sauce OnDemand Plug-in v1.142 , SauceConnect v4.3.11

      SauceConnect fails to launch using the OnDemand plugin in Jenkins, failing builds.
      There is no problem on Command Prompt since it is showing :
      Sauce Connect is up, you may start your tests.

      However the Jenkins fails the build with following errors:

      *Starting pre-build for Sauce Labs plugin
      Starting Sauce Connect on master node using identifier: default
      Launching Sauce Connect on ECS-8110eee4.ecs.ads.autodesk.com
      Error launching Sauce Connect
      Flushing Sauce Connect Input Stream
      Flushing Sauce Connect Error Stream
      Closing Sauce Connect process
      FATAL: Error launching Sauce Connect
      com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect
      at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:320)
      at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:841)
      at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:327)
      at hudson.model.Build$BuildExecution.doRun(Build.java:154)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
      at hudson.model.Run.execute(Run.java:1759)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:89)
      at hudson.model.Executor.run(Executor.java:240)*

            halkeye Gavin Mogan
            hedieh Hedieh ekhlasi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: