-
Bug
-
Resolution: Fixed
-
Minor
-
-
2.429
After upgrading from 2.426 to 2.427 stdout and stderr is no longer returned to the client.
I started a fresh Jenkins, and created an admin account, downloaded the jenkins-cli.jar and ran a simple command, that should write Hello! on the terminal.
docker run -p 8080:8080 jenkins/jenkins:2.427-jdk17
wget http://localhost:8080/jnlpJars/jenkins-cli.jar
echo 'println "Hello!"' | java -jar jenkins-cli.jar -auth admin:admin -s http://localhost:8080/ groovy =
It appears to be related til https://issues.jenkins.io/browse/JENKINS-41516, and creating a logger for jenkins.util.DefaultScriptListener results in rather large stacktraces everytime any output is generated for a script.
- is caused by
-
JENKINS-41516 Groovy script console actions should be logged
-
- Closed
-
- links to
[JENKINS-72181] Jenkins-cli groovycommand does not return stdout (regression in 2.427)
Link |
New:
This issue is caused by |
Summary | Original: Jenkins-cli groovycommand does not return stdout | New: Jenkins-cli groovycommand does not return stdout (regression in 2.427) |
Labels | New: regression |
Assignee | New: Daniel Beck [ danielbeck ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Component/s | New: core [ 15593 ] |
Remote Link | New: This issue links to "PR#8622 (Web Link)" [ 28989 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |