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

jenkinsfile-runner needs verbose output or logs

    Details

    • Similar Issues:

      Description

      jenkinsfile-runner looks awesome, but it doesn't give any meaningful output when it fails. There seems to be no verbose mode and no obvious log files with useful output. The docs lack any kind of troubleshooting guide, so I'm basically no able to evaluate this further.

      docker run -it -v $PWD/jenkinsfile-runner:/var/jenkinsfile-runner -v $PWD/smartly-ansible:/workspace  -v jenkinsfile-runner-cache:/var/jenkinsfile-runner-cache jenkins/jenkinsfile-runner
      Downloading latestCore ...
      Running Pipeline on jenkins 2.138.1
      Starting Jenkins...
      Running from: /var/jenkinsfile-runner-cache/war/jenkins-2.138.1.war
      webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
      Jenkins home directory: /var/jenkinsfile-runner found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
      Started
      Running in Durability level: PERFORMANCE_OPTIMIZED
      cmd.Start() failed with exit status 255Something went wrong running your Jenkinsfile.
      If you think this is a bug, please report on https://github.com/ndeloof/jenkinsfile-runner/issues
      and if you miss some feature, please join https://gitter.im/jenkinsci/jenkinsfile-runner to discuss about it.
      

       

        Attachments

          Activity

          Hide
          ndeloof Nicolas De Loof added a comment -

          pipeline execution only reports
          cmd.Start() failed with exit status 255
          nothing more we can offer, until pipeline has some extra verbose mode we can enable ?

          Show
          ndeloof Nicolas De Loof added a comment - pipeline execution only reports cmd.Start() failed with exit status 255 nothing more we can offer, until pipeline has some extra verbose mode we can enable ?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          I agree with the comment from Nicolas De Loof, we cannot offer better diagnostics in JFR for this case.

          There is an option to set higher system logging level in JFR via system properties, and it fully covers the Jenkins system logging.

           

          Show
          oleg_nenashev Oleg Nenashev added a comment - I agree with the comment from Nicolas De Loof , we cannot offer better diagnostics in JFR for this case. There is an option to set higher system logging level in JFR via system properties, and it fully covers the Jenkins system logging.  
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Resolving, because there was no follow-up from the reporter, and it is not clear what is the expectation

          Show
          oleg_nenashev Oleg Nenashev added a comment - Resolving, because there was no follow-up from the reporter, and it is not clear what is the expectation

            People

            • Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              peterjenkins Peter Jenkins
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: