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

Sauce Connect does not close when used with Pipelines

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      A customer has reported that they're seeing Sauce Connect stay open until manually killed once they migrated to pipelines.

      According to their logs, the Sauce Connect part of the pipeline opens properly, finishes cleanly, and the SC logs show that SC continues to run until terminated (See the snipped up logs below).

      They are using the current (1.155) version of the Sauce OnDemand Plugin.

      Pipeline Logs

      [Pipeline] sauceconnect
      Starting sauce connect
      /bin/sc already exists, so not extracting
      07 Sep 18:46:29 - Sauce Connect 4.3.16, build 2396 39e807b
      
      <snip>
      
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD SUCCESS
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 39.497 s
      [INFO] Finished at: 2016-09-07T18:47:30+00:00
      [INFO] Final Memory: 24M/349M
      [INFO] ------------------------------------------------------------------------
      [Pipeline] }
      [Pipeline] // wrap
      [Pipeline] }
      [Pipeline] // sauceconnect
      [Pipeline] }
      [Pipeline] // sauce
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] End of Pipeline
      Finished: SUCCESS
      

      End of Sauce Connect logs

      20160907 184732.927 [04001] PROXY 127.0.0.1:60702 <- 301 url:80 (777 bytes)
      20160908 000801.152 [04001] Warning: Remote tunnel VM has been terminated by user request. Shutting down.
      20160908 000801.152 [04001] Cleaning up.
      

      Note the timestamps of the last request and when the tunnel was shutdown by the user, as well as the timestamp of Maven when the build finished.

      Digging through the code, it looks like maybe the process is just abandoned at the end of the pipeline step?

        Attachments

          Activity

          dylanlacey Dylan Lacey created issue -
          halkeye Gavin Mogan made changes -
          Field Original Value New Value
          Description A customer has reported that they're seeing Sauce Connect stay open until manually killed once they migrated to pipelines.

          According to their logs, the Sauce Connect part of the pipeline opens properly, finishes cleanly, and the SC logs show that SC continues to run until terminated (See the snipped up logs below).

          They are using the current (1.155) version of the Sauce OnDemand Plugin.

          h2. Pipeline Logs
          {{[Pipeline] {
          [Pipeline] sauceconnect
          Starting sauce connect
          /bin/sc already exists, so not extracting
          07 Sep 18:46:29 - Sauce Connect 4.3.16, build 2396 39e807b

          <snip>

          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 39.497 s
          [INFO] Finished at: 2016-09-07T18:47:30+00:00
          [INFO] Final Memory: 24M/349M
          [INFO] ------------------------------------------------------------------------
          [Pipeline] }
          [Pipeline] // wrap
          [Pipeline] }
          [Pipeline] // sauceconnect
          [Pipeline] }
          [Pipeline] // sauce
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] End of Pipeline
          Finished: SUCCESS}}

          h3. End of Sauce Connect logs
          {{20160907 184732.927 [04001] PROXY 127.0.0.1:60702 <- 301 url:80 (777 bytes)
          20160908 000801.152 [04001] Warning: Remote tunnel VM has been terminated by user request. Shutting down.
          20160908 000801.152 [04001] Cleaning up.}}

          Note the timestamps of the last request and when the tunnel was shutdown by the user, as well as the timestamp of Maven when the build finished.

          Digging through the code, it looks like maybe the process is just abandoned at the end of the pipeline step?
          A customer has reported that they're seeing Sauce Connect stay open until manually killed once they migrated to pipelines.

          According to their logs, the Sauce Connect part of the pipeline opens properly, finishes cleanly, and the SC logs show that SC continues to run until terminated (See the snipped up logs below).

          They are using the current (1.155) version of the Sauce OnDemand Plugin.

          h2. Pipeline Logs
          {code}
          [Pipeline] sauceconnect
          Starting sauce connect
          /bin/sc already exists, so not extracting
          07 Sep 18:46:29 - Sauce Connect 4.3.16, build 2396 39e807b

          <snip>

          [INFO] ------------------------------------------------------------------------
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 39.497 s
          [INFO] Finished at: 2016-09-07T18:47:30+00:00
          [INFO] Final Memory: 24M/349M
          [INFO] ------------------------------------------------------------------------
          [Pipeline] }
          [Pipeline] // wrap
          [Pipeline] }
          [Pipeline] // sauceconnect
          [Pipeline] }
          [Pipeline] // sauce
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] End of Pipeline
          Finished: SUCCESS
          {code}

          h3. End of Sauce Connect logs
          {code}
          20160907 184732.927 [04001] PROXY 127.0.0.1:60702 <- 301 url:80 (777 bytes)
          20160908 000801.152 [04001] Warning: Remote tunnel VM has been terminated by user request. Shutting down.
          20160908 000801.152 [04001] Cleaning up.
          {code}

          Note the timestamps of the last request and when the tunnel was shutdown by the user, as well as the timestamp of Maven when the build finished.

          Digging through the code, it looks like maybe the process is just abandoned at the end of the pipeline step?
          halkeye Gavin Mogan made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]

            People

            Assignee:
            halkeye Gavin Mogan
            Reporter:
            dylanlacey Dylan Lacey
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: