Setting Plan variables

The default, and recommended, scope of variables extracted with the plugin is the build result.  You have the option of setting Plan level variables instead.  If you use this feature, please note the following. You will not be able to access a newly created Plan variable within the context of the job that you extract and set it. Plan variables are effectively locked for the entire execution of a specific build and for downstream things like linked Deployment Projects. This means that when the build kicks off, the Plan variables become set in stone. Any new Plan variables you set or any changes to Plan variables that you make within the context of that build will not take effect until the next build executes.  See the comments on Issue #3 for more details.