I successfully convinced Maven to run my mvn:deploy/mvn:site-deploy targets after following the (very ugly) workaround described here http://debalex.wordpress.com/2008/10/07/maven-site-deployment-inside-hudson/. Now after upgrading TC-installation, agents upgraded as well and now my deploy targets are _failing_ again due to some overwritten (?) configuration of the build agent. Note there is no standalone M2 installation on this agent, and it didn't fail on my notebook where there is one (even after upgrading build agent).
So my questions are:
What settings did get destroyed here?
How can I prevent this workaround on updating my agents?
Would it be possible for Teamcity to distribute public key fingerprints to the agents automatically in order not to have to apply this workaround on every single build-agent?
There must be some better solution..