One use of envlnject which i have used Create a standard java .properties file and you can fetch the environmental variable and these can be used during your job. you need to specify the properties file in your job configuration. One way to do it copy the properties file from your slave node/master node to $WORKSPACE.
cp /root/build.properties $WORKSPACE/ here build.properties file is the standard java properties file. On Friday, 23 October 2015 20:25:08 UTC+5:30, Martin d'Anjou wrote: > > A while ago, I was able to use the envinject plugin to set the workspace > path, but it does do that anymore. I wish I could control the workspace > location for two reasons: > 1) I need to share workspaces between jobs because of the large volume of > data being produced (archiving is not practical) > 2) Gradle is unable to continue a build when the absolute path to the > build output changes > <https://discuss.gradle.org/t/incremental-build-state-should-be-decoupled-from-workspace-location/505> > . > > Q) Is the envinject supposed to be able to control the workspace location? > > Thanks, > Martin > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c72b6743-13a7-4a46-b751-b25f7ba7db37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
