• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None

      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).

          [JENKINS-5296] Commands not printed during remote builds

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue depends on JENKINS-4479 [ JENKINS-4479 ]
          Jesse Glick made changes -
          Summary Original: No indication that a build is waiting for a workspace lock New: Commands not printed during remote builds
          Jesse Glick made changes -
          Link Original: This issue depends on JENKINS-4479 [ JENKINS-4479 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 135385 ] New: JNJira + In-Review [ 203451 ]

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: