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

UI doesn't show all errors

    XMLWordPrintable

Details

    • iapetus, 1.0

    Description

      When something similar (variable is not defined in Jenkinsfile) occurs - there is nothing in UI about this error. Only status is RED. No messages at all. But full log contains an error:

      [Bitbucket] Notifying commit build result
      [Bitbucket] Build result notified
      groovy.lang.MissingPropertyException: No such property: DEPLOY_ENV for class: groovy.lang.Binding
      	at groovy.lang.Binding.getVariable(Binding.java:63)
      	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224)
      	at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)
      	..bla bla bla
      Finished: FAILURE
      

      Attachments

        Activity

          jamesdumay James Dumay added a comment -

          vivek we may want to cover this use case in the error step reporting.

          kamikaze would you be able to provide a small Jenkinsfile that reproduces a similar error?

          jamesdumay James Dumay added a comment - vivek we may want to cover this use case in the error step reporting. kamikaze would you be able to provide a small Jenkinsfile that reproduces a similar error?
          vivek Vivek Pandey added a comment -

          jamesdumay We do capture any error thats captured during pipeline run and they are shows in the respective step's logs. Even if error happens outside of step/stage, such logs are wrapped to closest step.

          This particular case where pipeline was not even executed, we can't show log in context of a stage/parallel/step. What UI can perhaps do in this case is to show full log if there are no nodes?

          vivek Vivek Pandey added a comment - jamesdumay We do capture any error thats captured during pipeline run and they are shows in the respective step's logs. Even if error happens outside of step/stage, such logs are wrapped to closest step. This particular case where pipeline was not even executed, we can't show log in context of a stage/parallel/step. What UI can perhaps do in this case is to show full log if there are no nodes?
          jamesdumay James Dumay added a comment -

          vivek could you try to reproduce this for me and see if the UI responds in the way that it should?

          jamesdumay James Dumay added a comment - vivek could you try to reproduce this for me and see if the UI responds in the way that it should?
          vivek Vivek Pandey added a comment -

          jamesdumay Yes, UI does the right thing. I think we are good.

          node{
              sh "echo '${myparam}'"
          }
          

          vivek Vivek Pandey added a comment - jamesdumay Yes, UI does the right thing. I think we are good. node{ sh "echo '${myparam}' " }
          jamesdumay James Dumay added a comment -

          kamikaze what were you hoping to see here?

          jamesdumay James Dumay added a comment - kamikaze what were you hoping to see here?
          jamesdumay James Dumay added a comment -

          vivek ill take this one until we get a response from Oleg

          jamesdumay James Dumay added a comment - vivek ill take this one until we get a response from Oleg
          jamesdumay James Dumay added a comment -

          When we get an error from the compilation phase of executing the groovy DSL we are unable to get the model to display better errors as steps.

          jamesdumay James Dumay added a comment - When we get an error from the compilation phase of executing the groovy DSL we are unable to get the model to display better errors as steps.

          People

            jamesdumay James Dumay
            kamikaze Oleg Korsak
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: