-
Bug
-
Resolution: Cannot Reproduce
-
Blocker
-
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
- is related to
-
-
- Resolved
-
[JENKINS-8471] Freestyle jobs no longer pipe stdout to the console
randon
made changes -
| Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
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. 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.
| Link |
New:
This issue is related to |
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
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
This issue is breaking all of our builds.