Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
If there is problem with SCM polling hanging (as in JENKINS-4461) and you try to manually start a job, Hudson will duly schedule it on an executor and then seem to run it. When you look at the console, it says e.g.
--%<--
Console Output
--------------
Started by user jglick
Building remotely on someslave
--%<--
and then nothing else happens - indefinitely. This is not friendly.
If the build has to wait to acquire a workspace lock, it should say so... and give you information about how to kill any outstanding polling process (JENKINS-4479).
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue depends on JENKINS-4479 [ JENKINS-4479 ] |
| Summary | No indication that a build is waiting for a workspace lock | Commands not printed during remote builds |
| Link | This issue depends on JENKINS-4479 [ JENKINS-4479 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Workflow | JNJira [ 135385 ] | JNJira + In-Review [ 203451 ] |