|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

You can pass it as a job parameter. For example you'd have a String parameter for the job named "BUILD_NUMBER" and in the specific build number field you reuse that with "$BUILD_NUMBER".
Varaibles are expanded so I don't see why it wouldn't work with envinject. From what I see, inject a variable named "DOWNSTREAM_JOB_BUILD_NUMBER1" and affect it with "$DOWNSTREAM_JOB_BUILD_NUMBER".
[EnvInject] - Injecting as environment variables the properties content
DOWNSTREAM_JOB_BUILD_NUMBER1=$DOWNSTREAM_JOB_BUILD_NUMBER
So the variable can be expanded in "$DOWNSTREAM_JOB_BUILD_NUMBER1" which is not a build number. Moreover, if you only injected this, there's no "$DOWNSTREAM_JOB_BUILD_NUMBER" variable.