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

Freestyle jobs no longer pipe stdout to the console

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • core
    • None

      I no longer get the output from the shellscript/console that I execute through my freestyle job piped to the job, so that it appers in the console log.
      All I get is:

      11:22:17 Started by user et2448 11:22:17 Building remotely on aat-efs-app01-as-jetty 11:22:17 [deploy-pays-eosk] $ /bin/sh /tmp/hudson877385952895158332.sh

          [JENKINS-8471] Freestyle jobs no longer pipe stdout to the console

          aggamemnon added a comment -

          This issue is breaking all of our builds.

          aggamemnon added a comment - This issue is breaking all of our builds.

          fpesquet added a comment -

          Still the case with 1.393.
          Notice that with 1.393 this works with Windows slaves launched through JNLP (i.e. output from job appear to console log), while it fails with Unix slaves launched through ssh (i.e. output from jobs does NOT appear to console log).

          fpesquet added a comment - Still the case with 1.393. Notice that with 1.393 this works with Windows slaves launched through JNLP (i.e. output from job appear to console log), while it fails with Unix slaves launched through ssh (i.e. output from jobs does NOT appear to console log).

          kevinp2 added a comment -

          Verified as a known issue in 1.390

          This is a serious problem and makes it difficult to troubleshoot new jobs or jobs with problems because the console log is lost.

          kevinp2 added a comment - Verified as a known issue in 1.390 This is a serious problem and makes it difficult to troubleshoot new jobs or jobs with problems because the console log is lost.

          qinqon added a comment -

          We have found a workaround for it, cleaning the hudson stuff in the slaves (classworlds.jar maven2.1-interceptor.jar maven3-agent.jar maven3-interceptor.jar maven-agent.jar maven-interceptor.jar plexus-classworld.jar) and restarting them. We have also restarted hudson machine.

          qinqon added a comment - We have found a workaround for it, cleaning the hudson stuff in the slaves (classworlds.jar maven2.1-interceptor.jar maven3-agent.jar maven3-interceptor.jar maven-agent.jar maven-interceptor.jar plexus-classworld.jar) and restarting them. We have also restarted hudson machine.

          What OS&JDK are you having this problem on?

          Baptiste Mathus added a comment - What OS&JDK are you having this problem on?

          I'm linking to JENKINS-8420 though I'm not totally sure this is related.
          Might help users that find this bug report first having the "no more logs" issue.

          Baptiste Mathus added a comment - I'm linking to JENKINS-8420 though I'm not totally sure this is related. Might help users that find this bug report first having the "no more logs" issue.

          After some experiments:
          It was an incompatibility with IBM JDK 1.5.
          Using JDK SUN 1.6 to launch slave fixes the issue.
          With Hudson <=1.386, IBM JDK 1.5 was working also. So this was a kind of regression.

          This regression was fixed presumably with JENKINS-8420 :
          retrying with Jenkins >= 1.403, all seems to work whatever the JDK
          => I think this defect can be closed, at least for me

          Frederic Pesquet added a comment - After some experiments: It was an incompatibility with IBM JDK 1.5. Using JDK SUN 1.6 to launch slave fixes the issue. With Hudson <=1.386, IBM JDK 1.5 was working also. So this was a kind of regression. This regression was fixed presumably with JENKINS-8420 : retrying with Jenkins >= 1.403, all seems to work whatever the JDK => I think this defect can be closed, at least for me

          Rene Zbinden added a comment -

          I have the same problem here, I tried the following versions:
          jenkins-1.396-1.1.noarch.rpm
          jenkins-1.399-1.1.noarch.rpm
          jenkins-1.400-1.1.noarch.rpm
          jenkins-1.403-1.1.noarch.rpm
          jenkins-1.413-1.1.noarch.rpm
          jenkins-1.414-1.1.noarch.rpm

          Does someone know a version that works?

          BR, Rene

          Rene Zbinden added a comment - I have the same problem here, I tried the following versions: jenkins-1.396-1.1.noarch.rpm jenkins-1.399-1.1.noarch.rpm jenkins-1.400-1.1.noarch.rpm jenkins-1.403-1.1.noarch.rpm jenkins-1.413-1.1.noarch.rpm jenkins-1.414-1.1.noarch.rpm Does someone know a version that works? BR, Rene

          sogabe added a comment -

          reopen if reproduced.

          sogabe added a comment - reopen if reproduced.

            Unassigned Unassigned
            davidkarlsen davidkarlsen
            Votes:
            10 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: