mvn:deploy, SCP & unknown_hosts

Hi,

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..

Thanks,

Yann

3 comments
Comment actions Permalink

The BuildAgent-update problem was actually a misconfiguration w/r to settings.xml. Still, the initial problem of getting maven's SCP to work on a freshly installed buildagent is still there.

0
Comment actions Permalink

Hello Yann,

This is a known problem. However, we still don't have a means for not overwriting
config files during upgrades. The workaround for this problem is to put non-default
settings.xml into a special location and tell Maven runner to use it (the
runner settings page has a special field for that). This will guarantee the
safety of your settings during upgrades.

If you have many agents and don't want to place settings.xml into the same
path on all agents, a good solution would be to define a system property
(say, maven.settings.path) for each agent and just refer to it in the runner
settings in the following form - %maven.settings.path%

We've been thinking of providing an ability of pushing various data to agents
from the server in a centralized way. This is what you might apreciate as
a solution for your problem. However I can't tell you now when it's going
to be implemented. :(

Sorry for inconvenience, and thank you for reporting.

The BuildAgent-update problem was actually a misconfiguration w/r to
settings.xml. Still, the initial problem of getting maven's SCP to
work on a freshly installed buildagent is still there.

---
Original message URL:
http://www.jetbrains.net/devnet/message/5233695#5233695

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hello Sergey,

thanks for your response.

Indeed I put my settings.xml into /home/teamcity/.m2 (a repository has to be there anyway) so it will survive in the future ;-).

Best regards,
Yann

0

Please sign in to leave a comment.