Jenkins Cannot define variable in pipeline stage

Question

I m trying to create a declarative Jenkins pipeline script but having issues with simple variable declaration   Here is my script   pipeline      agent none    stages          stage  first                def foo    foo     fails with  WorkflowScript  5  Expected a step   line 5  column 13              sh  echo   foo                     However  I get this error   org codehaus groovy control MultipleCompilationErrorsException  startup failed  WorkflowScript  5  Expected a step   line 5  column 13             def foo    foo                 I m on Jenkins 2 7 4 and Pipeline 2 4

User · Accepted Answer

The Declarative model for Jenkins Pipelines has a restricted subset of syntax that it allows in the stage blocks - see the syntax guide for more info  You can bypass that restriction by wrapping your steps in a script         block  but as a result  you ll lose validation of syntax  parameters  etc within the script block

User · Answer

You are using a Declarative Pipeline which requires a script-step to execute Groovy code  This is a huge difference compared to the Scripted Pipeline where this is not necessary   The official documentation says the following      The script step takes a block of Scripted Pipeline and executes that   in the Declarative Pipeline    pipeline      agent none    stages          stage  first                script                  def foo    foo                  sh  echo   foo

User · Answer

I think error is not coming from the specified line but from the first 3 lines  Try this instead   node      stage  quot first quot          def foo    quot foo quot       sh  quot echo   foo  quot          I think you had some extra lines that are not valid    From declaractive pipeline model documentation  it seems that you have to use an environment declaration block to declare your variables  e g   pipeline      environment        FOO    quot foo quot           agent none    stages          stage  quot first quot                sh  quot echo   FOO  quot

User · Answer

Agree with  Pom12   abayer  To complete the answer you need to add script block Try something like this  pipeline       agent any     environment           ENV NAME    quot   env BRANCH NAME  quot                ----------------      stages           stage  Build Container                 steps                   echo  Building Container                     script                       if  ENVIRONMENT NAME     development                             ENV NAME    Development                        else if  ENVIRONMENT NAME     release                             ENV NAME    Production                                                          echo  Building Branch      env BRANCH NAME                 echo  Build Number      env BUILD NUMBER                 echo  Building Environment      ENV NAME                  echo  quot Running your service with environemnt   ENV NAME  now quot

User · Answer

you can define the variable global   but when using this variable must to write in script block   def foo  quot foo quot  pipeline   agent none stages      stage  quot first quot           script            sh  quot echo   foo  quot

User · Answer

In Jenkins 2 138 3 there are two different types of pipelines   Declarative and Scripted pipelines    Declarative pipelines is a new extension of the pipeline DSL  it is basically a pipeline script with only one step  a pipeline step with arguments  called directives   these directives should follow a specific syntax  The point of this new format is that it is more strict and therefore should be easier for those new to pipelines  allow for graphical editing and much more  scripted pipelines is the fallback for advanced requirements    jenkins pipeline  agent vs node   Here is an example of using environment and global variables in a Declarative Pipeline   From what I can tell enviroment are static after they are set   def  browser    Unknown   pipeline       agent any     environment         Use Pipeline Utility Steps plugin to read information from pom xml into env variables     IMAGE   readMavenPom   getArtifactId       VERSION   readMavenPom   getVersion               stages           stage  Example                 steps                   script                       browser   sh returnStdout  true  script   echo Chrome                                                     stage  SNAPSHOT                     when                       expression                            return  env JOB NAME equals  PROD    amp  amp   env VERSION contains  RELEASE                                                           steps                       echo  SNAPSHOT                      echo    browser                                               stage  RELEASE                     when                       expression                            return  env JOB NAME equals  TEST    amp  amp   env VERSION contains  RELEASE                                                           steps                       echo  RELEASE                      echo    browser                                          end of stages     end of pipeline

[jenkins] Jenkins: Cannot define variable in pipeline stage

Examples related to jenkins

Examples related to groovy

Examples related to jenkins-pipeline