Set variables after completed OpenShift Jenkins Build Step about jenkins-plugin HOT 3 CLOSED

I've looked into this in the past and found that EnvVars I set in one step were not available in subsequent steps. But since then, I've learned that I might have needed something like the EnvInject plugin to get this to work.

Now, we've got a bunch of in-progress work around Jenkins Pipelines that are for example setting annotations on the OpenShift builds themselves to allow for the type of correlations I believe you are referring to.

So, moving forward on this issue would entail

1. gathering/receiving intel on the mechanics needed to set/receive env vars between classic jenkinst freestyle steps
2. discussions with OpenShift architecture on reconciling the different ways we want to correlate environment information in our jenkins scenarios

@bparees @smarterclayton @spadgett @jimmidyson @rawlingsj FYI

from jenkins-plugin.

@gabemontero let's open this as a card on the trello backlog and close this issue.

from jenkins-plugin.

trello card on devexp backlog: https://trello.com/c/uPfbMfwT/986-exchange-environment-variable-between-jenkins-build-steps

from jenkins-plugin.