[JENKINS-56413] Option failFast in declarative pipeline does not support variables

In a declarative pipeline, we have some parallel steps. On start of a build, the user should be able to decide whether the steps should fail fast or not.

Thus, we introduced a boolean parameter "FAIL_FAST" and used it in the step like this:

stage('Smoke Test') {

    failFast params.FAIL_FAST

    parallel {

        ...

However, that led to following exception:

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

WorkflowScript: 196: Expected a boolean with failFast @ line 196, column 7.

     failFast params.FAIL_FAST

     ^

It should be possible to use variables at this point.

---
Originally reported by chamshoff, imported from: Option failFast in declarative pipeline does not support variables

• status: Open
  
• priority: Major
  
• component(s): pipeline
  
• label(s): pipeline
  
• resolution: Unresolved
  
• votes: 4
  
• watchers: 4
  
• imported: 2025-12-08
  

Raw content of original issue

In a declarative pipeline, we have some parallel steps. On start of a build, the user should be able to decide whether the steps should fail fast or not.


Thus, we introduced a boolean parameter "FAIL_FAST" and used it in the step like this:


stage('Smoke Test') {

     failFast params.FAIL_FAST

     parallel {

         ...


However, that led to following exception:


org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

 WorkflowScript: 196: Expected a boolean with failFast @ line 196, column 7.

      failFast params.FAIL_FAST

      ^


It should be possible to use variables at this point.

The issue names no repository files or tests. Start by reproducing the declarative pipeline example with a boolean parameter and the failFast validation error; done means a variable such as params.FAIL_FAST is accepted and controls whether parallel steps fail fast.

Written by the indexing model from the issue text.