Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5296

Commands not printed during remote builds

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • core
    • 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

          People

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

            Dates

              Created:
              Updated:
              Resolved: