[JIRA] (JENKINS-15112) Injected Jenkins build env variables not resolved/forwarded

Wed, 26 Dec 2012 12:29:56 -0800

I'm sorry for my late reply.
Firstly, EnvInject plugin and Artifactory plugin are independent. The main goal of EnvInject plugin is to provide the ability to inject environment variables before a SCM checkout, after a SCM checkout, at a build step and at a post build step.

For each build, all injected environment variables can be retrieved through the dashboard, through a file (multiple format are available, default is txt) in the build directory in the JENKINS_HOME, by REST API (refer to the wiki plugin page).

For your use cas, you are able to load your data.properties from the EnvInject plugin and keys will be exported as environment variable names.
After I don't know how to integrate it with the Artifactory plugin

EnvInject is for now an important plugin in the Jenkins ecosystem and it is the only way to manage properly your job environment variables.
If Artifactory plugin gather environment variables before the end of the EnvInject plugin, the conclusion is: Artifactory plugin doesn't gather the right environment variables.
Therefore, there are two solutions:
1) Artifactory evolves
2) Switch your job to a more suited plugin
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

Reply via email to