End SSH Session
N
Nchowdhury@cargurus.com
This is an old issue but I do want to bring up that with job groups this becomes even more necessary if you want to troubleshoot the last job in a group. Right now you have to wait 10 minutes for each previous job in the group to kill the ssh session before it actually gets to the job you are trying to troubleshoot. With 2 or 3 jobs thats a half hour!
T
Trenton Collier
@x trench run Has this issue been resolved?
J
Jonas Lohardt Havlykke
Had the same issue. I ended up using sudo reboot. That worked.
K
Keisuke Shioya
Agree. My plan is "2 Containers".
If I create two SSH jobs, CI won't work for two hours after I turn off the session.
M
Mihai Matache
The fact that I can't quit a job is ridiculous... And it's on a free account, so it's on your dime :|
Jamie
Wow. Is this really still an issue?!
A
Abdullah Saleem
Same issue, with 1 pipeline at a time execution the jobs are stuck
B
Boris Lapouga
Agree, all our tests hanged when we requested SSH shell with parallelism of 25 enabled, can't even disable it now, complete stall.
Janak Shah
Agree
M
Matthew Morrissette vance
Yes but then that causes the build to show as cancelled instead of what the true result was.
Load More
→