On 25/01/10 12:47 PM, Gav... wrote:
What I think might be a better setup, is for projects to be able to deploy
to a temp staging area on the
Hudson Master. The Hudson master then has a special acct to be able to sync
to people. So, one restricted
specially setup acct from the master rather than m
> -Original Message-
> From: Aristedes Maniatis [mailto:a...@maniatis.org]
> Sent: Monday, 25 January 2010 11:34 AM
> To: builds@apache.org
> Subject: Re: publishing artifacts from hudson build node to
> people.apache.org
>
> I raised this on infra a little
I raised this on infra a little while ago and there was agreement that keeping
SSH keys on Hudson is pretty dangerous. At the least, the SSH user will need to
be able to change your live production web site. So any compromise of Hudson
servers will by default allow an attacker to change Apache
Thanks... So, you're doing it the other way around... interesting !
For the record, i've also found
http://struts.apache.org/2.1.8.1/docs/apache-struts-pseudo-nightly-builds-on-apache-hudson.html
which basically describes that the struts guys use the 'wesw' account
for sshing to people.apache.org
On 25/01/10 11:24 AM, Andreas Andreou wrote:
How are people making this work? Is any apache project using hudson to update
parts of their website?
Yes, I'm pulling Javadocs from Hudson like this:
http://svn.apache.org/repos/asf/cayenne/site/trunk/tlp-site/bin/deployJavadoc.sh
Ari
--
Hi,
I'd like to publish a maven generated site from a build node (in our case
vesta.apache.org) to people.apache.org
I see two options to do this:
1) issue mvn deploy
2) use hudson's scp plugin
I'm not comfortable with either solutions because both require me storing my
ssh credentials to the bui
