Valid use of environment directive

[Idan Adar]

Is this a valid use of environment directive and variables in declarative pipeline?

pipeline {
   environment {
       MY_VAR = null
   }  


   stages {
      stage ("...") {
         steps {
         MY_VAR = "this_stage"
         }
      }
      stage ("...") {
         steps {
         MY_VAR = "this_stage2"
         }
      }
  }
 
  post {
      success {
          slackSend (
            message: "$STAGE_NAME stage failed."
         )
      }
  }

}

[Idan Adar]

Perhaps Robert (CCed) can help?

[Danny Rehelis]

Encapsulate MY_VAR in script { } blocked required to set a variable when using declarative pipeline inside a Stage.

No need to declare it with-in environment { }.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/76f4796b-9bee-455f-8c95-decdff8da6fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Idan Adar]

Yes, that's how I do it in my actual Jenkinsfile, but I thought maybe in a Declarative pipeline this works differently...

[Andrew Bayer]

No, that's definitely not intended to work that way, and it probably won't work. 

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4c7b1a85-8fde-435a-bee2-45275b787aa1%40googlegroups.com.

[Idan Adar]

script { } it is... :/