I have installed Jenkins 1.409.1 and build-name-setter 1.3. I have enabled the build-name-setter for a free-stype software project and it works. However when I enable it for a multi-configuration job it does not work right. For the purposes of description I will refer to the multi-configuration job as the parent job, and to the individual jobs the defined in the Configuration Matrix as the child jobs. In the parent job configuration I set the build name to a simple string. Here is what happens: The parent job uses the standard incrementing build number rather than the string. The child jobs in the Configuration Matrix do correctly use the string as the build name. However if I use an environment variable as the build name, the child jobs' names are blank - as though the environment variables are not passed to the child jobs. Note the specific environment variable I tried to use in JOB-REVISION (comes from the version setter plugin I think).

Screen shot #1 is a free-style software project that works with the new build name (#3.0.18).
Screen shot #2 is a multi-configuration project (parent) - you can see that the build name is the incrementing number even though I've enabled the build-name-setter.
Screen shot #3 is one of the multi-configuration project's child jobs. You can see where it works with a simple string (FRED), but the blanks are attempts at using $(ENV,var="JOB_REVISION"}.

I am not sure if the fault lies in this plugin, or in the core Jenkins code that implements the multi-configuration job. Please advise if this bug should be reported to a different component.