Evironment not being passed through to the xUnit process about xunit-teamcity HOT 5 CLOSED

@JustinMorgan This is fixed in 1.1. I didn't know GitHub automatically closed issues when mentioned in a commit, and there is still just a prerelease. Sorry about that.

from xunit-teamcity.

Hi,
Thanks for the bug report! The environment should be passed along to the spawned process according to the java ProcessBuilder docs, but I'll try to verify this actually works. There might be some hoop-hopping since it is running within TeamCity.

from xunit-teamcity.

I've been experiencing this same issue and wondering if I was going crazy. I did a similar dump of the environment during the test run and got the exact same result: plenty of environment variables, but nothing that came from TeamCity. I think it must be an issue with the plugin--or with TeamCity itself--because the xunit console runner shouldn't be able to tell the difference between environment variables from TC and the ones already on the machine.

from xunit-teamcity.

Yeah, it's not in the xunit runner. It seems the teamcity agent might not initialize it's own environment as I had expected.
"Life happened" a bit last week, so I've been a bit tied up lately and unable to focus on this. I hope to have some progress soon, though.

from xunit-teamcity.

No sweat, thanks for the update. Other than this, the plugin has been really easy to use so far. I appreciate you putting it out there.

from xunit-teamcity.