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

Jenkins-cli groovycommand does not return stdout (regression in 2.427)

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • cli, core
    • 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.

          [JENKINS-72181] Jenkins-cli groovycommand does not return stdout (regression in 2.427)

          Per Agerbæk created issue -
          Basil Crow made changes -
          Link New: This issue is caused by JENKINS-41516 [ JENKINS-41516 ]
          Basil Crow made changes -
          Summary Original: Jenkins-cli groovycommand does not return stdout New: Jenkins-cli groovycommand does not return stdout (regression in 2.427)
          Basil Crow made changes -
          Labels New: regression
          Daniel Beck made changes -
          Assignee New: Daniel Beck [ danielbeck ]
          Daniel Beck made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Daniel Beck made changes -
          Component/s New: core [ 15593 ]

          Daniel Beck added a comment -

          Not the point, but just in case,

          rather large stacktraces everytime any output is generated for a script

          only applies if the logging level is FINEST. Log in FINER to get commands and output, FINE for just commands.

          Daniel Beck added a comment - Not the point, but just in case, rather large stacktraces everytime any output is generated for a script only applies if the logging level is FINEST. Log in FINER to get commands and output, FINE for just commands.
          Daniel Beck made changes -
          Remote Link New: This issue links to "PR#8622 (Web Link)" [ 28989 ]
          Daniel Beck made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]

            danielbeck Daniel Beck
            pagerbak Per Agerbæk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: