-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins: 2.263.4
OS: Linux - 3.10.0-1127.el7.x86_64
When using the "build -s " command in the cli to wait for the job to finish, and pass any interrupts to the job it works fine it the job was started, it will then be properly aborted. However, if the job is waiting in the queue, it will not be dequeued, instead it will be left there, orphaned. This makes the " -s " switch more or less useless, and I don't think there is a work-around.
Hey mats_johnson, thanks for reporting this. It sounds like this should be easy to reproduce. Would you be interested in opening a PR that simply adds a test case demonstrating the problem? The test would be expected to fail, obviously. Getting a reproducible test case in code form would be the first step toward resolving this issue.