Hi folks,

Many of our Declarative Pipeline jobs start off by printing environment 
variables, which aids in debugging (should that be necessary). In other 
words, the first stage of every job includes this step:
sh "env | sort"

Is it possible to hook this into all pipelines automatically, e.g. with a 
"pipeline decorator" or metaprogramming? Alternatively, is there a better 
solution for inspecting the ENV of builds which have already completed?

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b5e83af4-9584-4849-8730-85b0bd2191b7%40googlegroups.com.

Reply via email to