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

catchError - Expecting "class hudson.model.Result" for parameter "buildResult"

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: pipeline
    • Labels:
      None
    • Environment:
    • Similar Issues:
    • Released As:
      workflow-basic-steps 2.18

      Description

      Used pipeline:

      pipeline {
          agent any
          stages {
              stage('catch error') {
                  steps {
                      catchError(buildResult: 'SUCCESS') {
                          sh "exit 1"
                      }
                  }
              }
              stage('summary') {
                  steps {
                      echo "here comes the summary..."
                  }
              }
          }
      }
      

      Result:

      Running in Durability level: MAX_SURVIVABILITY
      org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
      WorkflowScript: 6: Expecting "class hudson.model.Result" for parameter "buildResult" but got "SUCCESS" of type class java.lang.String instead @ line 6, column 41.
               catchError(buildResult: 'SUCCESS')
                                       ^
      
      1 error
      
      	at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
      	at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
      	at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
      	at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
      	at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
      	at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
      	at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
      	at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
      	at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
      	at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:133)
      	at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:126)
      	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561)
      	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522)
      	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320)
      	at hudson.model.ResourceController.execute(ResourceController.java:97)
      	at hudson.model.Executor.run(Executor.java:429)
      Finished: FAILURE
      

       

        Attachments

          Issue Links

            Activity

            Hide
            dnusbaum Devin Nusbaum added a comment -

            Andrei Muresianu Yes, it should turn yellow in your example. I think that JENKINS-57579 is that problem, and we are waiting on a Blue Ocean fix to be merged and released to fix it. (In some cases, things work without the fix, but I think sequential stages are problematic.)

            Show
            dnusbaum Devin Nusbaum added a comment - Andrei Muresianu  Yes, it should turn yellow in your example. I think that  JENKINS-57579 is that problem, and we are waiting on a Blue Ocean fix to be merged and released to fix it. (In some cases, things work without the fix, but I think sequential stages are problematic.)
            Hide
            wamcubs Andrew Mullens added a comment -

            Hello, Did anyone ever solve this issue for Declarative pipeline? The catchError still give the same error.

            Show
            wamcubs Andrew Mullens added a comment - Hello, Did anyone ever solve this issue for Declarative pipeline? The catchError still give the same error.
            Hide
            dnusbaum Devin Nusbaum added a comment -

            Andrew Mullens Yes, this issue is fixed, see this comment. Make sure you are passing a String to catchError and not an object of type Result. If that still isn't working for you, please post an extract from your Jenkinsfile showing how you are using catchError.

            Show
            dnusbaum Devin Nusbaum added a comment - Andrew Mullens Yes, this issue is fixed, see this comment . Make sure you are passing a String to catchError and not an object of type Result . If that still isn't working for you, please post an extract from your Jenkinsfile showing how you are using catchError .
            Hide
            wamcubs Andrew Mullens added a comment -

            Hey Devin, thank you. I saw that and was passing in a string, but turns out our Plug in Version is 2.66. So it should work once we update the plug in. Thanks again.

            Show
            wamcubs Andrew Mullens added a comment - Hey Devin, thank you. I saw that and was passing in a string, but turns out our Plug in Version is 2.66. So it should work once we update the plug in. Thanks again.
            Hide
            rbjorklin Robin Björklin added a comment - - edited

            Can anyone get the message to show?

            catchError(buildResult: 'SUCCESS', stageResult: 'SUCCESS', message: 'Not triggering downstream build.') {
                build job: "test/build", wait: false
            }
            

             EDIT: It shows up in the ConsoleText but not in Blue Ocean. Intended?

            Show
            rbjorklin Robin Björklin added a comment - - edited Can anyone get the message to show? catchError(buildResult: 'SUCCESS' , stageResult: 'SUCCESS' , message: 'Not triggering downstream build.' ) { build job: "test/build" , wait: false }  EDIT: It shows up in the ConsoleText but not in Blue Ocean. Intended?

              People

              • Assignee:
                dnusbaum Devin Nusbaum
                Reporter:
                twalter Torsten Walter
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: