I guess we could just run a script like this as an alternative on the Jenkins master so that the main workspace has access to the properties file:
That way we don't have to force Jenkins to double checkout the git repo per my older example.
There are a number of ways you could do this. The end goal is to make sure that the script runs on a regular basis or immediately after the jenkins workspace has polled the git repo.
For instance, you could have the script execute on the jenkins master directly through something as simple as a cron job.
Or, you could also try running it with a post-merge git hook in the workspace, that way it runs each time after a "git pull" occurs. Here is a basic example that you could modify for your needs:
If you're familiar with incron (http://inotify.aiken.cz/?section=incron&page=why&lang=en), you could have that daemon execute the script each time it notices a file change in the git checkout folder on the workspace.
... or just wait for this bug to get patched.
Hope this helps...