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

brokenBuildSuspects() returns empty list in pipeline script

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • email-ext-plugin
    • None
    • 2.67

      I created an empty git repository, added the following Jenkinsfile and created a Multibranch Pipeline for said repository:

      node
{
    try
    {
        stage('Build') 
        {
            echo 'starting build...'
            // foobar // uncomment to make it fail!!!
            echo 'build finished'
        }
    }
    catch(any)
    {
        currentBuild.result = 'FAILURE'

        emailext body: 'Someone broke your build.', mimeType: 'text/html', to: 'developer@mycompany.com', subject: 'Someone broke $PROJECT_NAME - Build $BUILD_NUMBER: $BUILD_STATUS'

        emailext body: 'You broke the build!', mimeType: 'text/html', recipientProviders: [brokenBuildSuspects()], subject: 'You broke $PROJECT_NAME - Build $BUILD_NUMBER: $BUILD_STATUS'
        throw any
    }

}

      When the pipeline is run, the build succeeds. Then I uncomment the line "foobar", commit the repo and the triggered build fails with the following console output:

      Branch event
Obtained Jenkinsfile from c49176e59c4d55c9f08c43b0994ea883e42d4c81
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on Jenkins in c:\ws\_master-DDKNEXKCSJHP2UWJJ
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] echo
starting build...
[Pipeline] }
[Pipeline] // stage
[Pipeline] emailext
Sending email to: developer@mycompany.com
[Pipeline] emailext
An attempt to send an e-mail to empty list of recipients, ignored.
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
groovy.lang.MissingPropertyException: No such property: foobar for class: groovy.lang.Binding
	at groovy.lang.Binding.getVariable(Binding.java:63)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264)
	at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:268)
	at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:268)
	at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29)
	at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
	at WorkflowScript.run(WorkflowScript:8)
	at ___cps.transform___(Native Method)
	at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
	at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
	at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
	at sun.reflect.GeneratedMethodAccessor336.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
	at com.cloudbees.groovy.cps.Next.step(Next.java:83)
	at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
	at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
	at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
	at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
	at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)
	at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)
	at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:182)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Finished: FAILURE

      As a result the first email to developer@mycompany.com is sent, but not the second mail to the suspects, because brokenBuildSuspects() seems to return an empty list. Likewise, culprits() returns an empty list, too.

      What am I doing wrong?

          [JENKINS-54940] brokenBuildSuspects() returns empty list in pipeline script

          Joerg Baeuerle added a comment -

          Maybe JENKINS-54163 is related? I've only seen it now.

          Joerg Baeuerle added a comment - Maybe JENKINS-54163 is related? I've only seen it now.

          Joerg Baeuerle added a comment -

          Any update on this? The mail notification feature for broken-build-suspects is crucial for us.

           

          Joerg Baeuerle added a comment - Any update on this? The mail notification feature for broken-build-suspects is crucial for us.  

          Emmanuel Ruhnau added a comment -

          Seems to be not working also for culprits()

          Emmanuel Ruhnau added a comment - Seems to be not working also for culprits()

          Basil Crow added a comment -

          Released in 2.67.

          Basil Crow added a comment - Released in 2.67 .

            slide_o_mix Alex Earl
            joerg_baeuerle Joerg Baeuerle
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: