-
Bug
-
Resolution: Fixed
-
Major
-
None
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?