Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Date: Wed, 16 Jun 2010 15:06:12 -0400
Message-ID: <AANLkTilTQ7oj9t6nv2jpT7hCqOoZ0x1I_TKfIcwP8ZCm@mail.gmail.com>
Subject: Suggestions for publishing to Ivy repo from Hudson using ssh
From: "Steele, Richard" <rich@steelezone.net>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=0016e640d01050912204892a6a67

--0016e640d01050912204892a6a67
Content-Type: text/plain; charset=ISO-8859-1

I'm trying to figure out the best way to handle publishing artifacts to our
Ivy repository using ssh.  We can't prompt the user for the username and
password since the publication is usually done by Hudson.  We can't embed
the username or password as a job configuration property because we can't
have those in cleartext; similarly, we can't use a standard user with a
well-known password in cleartext because of security concerns.

I'm leaning towards using a keystore, but we'd need to use one without a
password for the same reasons above (can't prompt, don't want to embed), but
a keystore without a password makes the security group twitchy.

I'm looking for any ideas or suggestions that might help; practical
experience with real examples would be best, but I'll consider anything.

Thanks,
Rich

--0016e640d01050912204892a6a67--