[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher

[langer...@gmail.com (JIRA)]

Rob Langley edited a comment on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher Just had a quick look at this and I don't think it's related to JENKINS-24467 - mostly as the code changed there shouldn't run during the build, only at poll time. In trying to repo this, I don't think it's due to expansion issue either, rather git credentials one. 2.2.5: + echo GIT_BRANCH_NAME=master [EnvInject] - Script executed successfully. [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path 'environments.properties' [EnvInject] - Variables injected successfully. Pushing HEAD to branch master at repo gitrepo > git config --get remote.gitrepo.url # timeout=10 > git push git@xxx:xxx/spaff.git HEAD:master Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS 2.2.6 + echo GIT_BRANCH_NAME=master [EnvInject] - Script executed successfully. [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path 'environments.properties' [EnvInject] - Variables injected successfully. Pushing HEAD to branch master at repo gitrepo > git push ${giturl} HEAD:master Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS I also added a build step to change a file during the build and this was successfully pushed using 2.2.6. So yes, in the log the env_var is not expanded but I don't think this it the cause of the issue. Config.xml (3k one, I should have used a different name) I used is attached, it's a simplified version of the one Thomas provided. This was tested using LTS 1.565.2. I think the repo you have Mark is a something different.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.