I've found it's a good practice to just run 'env' (or 'set' on Windows) in any shell steps whose environment I care about. Helps with weird machine-local /etc/profile and similar files as well, overriding what they should not be.
> On 30.08.2016, at 23:00, Wayne Warren <
wa...@puppet.com> wrote:
>
> Does anyone know how to view the build environment for a pipeline job? Is this built in to the pipeline job somehow and therefore needs no support from build-environment-plugin? I'd be happy to submit JIRA ticket for this and submit a patch if the fix isn't too time-consuming.
>
> It's pretty annoying that all I want to do is look at what environment variables are available for a particular build of the pipeline job and can't see it.
>
> --
> 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/2a1459ac-d5fb-4d89-9ac9-5d39f78392aa%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.