On Thu, Jun 16, 2011 at 11:54 AM, Niklas Gustavsson <[email protected]>wrote:

> On Thu, Jun 16, 2011 at 11:49 AM, Reto Bachmann-Gmuer
> <[email protected]> wrote:
> > This works fine when rnning site-deploy locally but not when having it
> > executed on hudson.   Would it be possible to give hudson the right to
> > access people.apache.org? Or should we configure things differently?
>
> There's been a few discussions on this topic previously. The problem
> boils down to build slaves being insecure, and thus we can't store
> private keys or similar that would enable Jenkins to access
> people.a.o.
>
I'm irritated that they are considered save enough for having credentials to
deploy to the maven artifact repository but not to the website server.

Cheers,
reto

Reply via email to