[JIRA] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase

[msz...@wp.pl (JIRA)]

Title: Message Title

Marcin Zajączkowski created an issue   Jenkins / JENKINS-30042 EnvInject doesn't see GIT_COMMIT even after SCM phase Issue Type: Bug Assignee: Manuel Jesús Recena Soto Components: envinject-plugin Created: 19/Aug/15 4:30 PM Environment: Jenkins 1.596.2 Environment Injector Plugin 1.92 GIT plugin 2.4.0 Priority: Minor Reporter: Marcin Zajączkowski Variables provided by Git plugin (tested with GIT_COMMIT) are not accessible in EnvInject plugin even if applied after SCM phase (Build Environment -> Inject environment variables to the build process). Sample Groovy code used in "Evaluated Groovy script": [GIT_COMMIT_SHORT: GIT_COMMIT] ends with: "[EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: null". It works wine with JOB_NAME or similar. GIT_COMMIT variable is later accessible in a build step. Sample Use case: Get a short version of Git commit SHA fetch by a job. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.