Storing encrypted password on Linux for automated builds with https://

[Alfred von Campe <al...@von-campe.com>]

We recently switched from svn+ssh:// to https:// access for Subversion on our Linux desktops, by configuring Subversion to store passwords in a secure manner using Gnome Keyring.  So far, so good.  The performance increase in checkouts, updates, logs, etc. is noticeable.  However, I haven’t been able to figure out how to get our automated builds, which run on headless servers, to use https:// for Subversion checkouts without requiring a password.  In case it matters, we are using Electric Commander for our builds.

I surely can’t be the first one to want to do this.  So what are the best practices surrounding automated builds and secure checkouts via https:// from Subversion servers?  I must be missing something obvious...

Alfred

Re: Storing encrypted password on Linux for automated builds with https://

[Branko Čibej <br...@wandisco.com>]

On 15.01.2015 16:16, Alfred von Campe wrote:
> We recently switched from svn+ssh:// to https:// access for Subversion on our Linux desktops, by configuring Subversion to store passwords in a secure manner using Gnome Keyring.  So far, so good.  The performance increase in checkouts, updates, logs, etc. is noticeable.  However, I haven’t been able to figure out how to get our automated builds, which run on headless servers, to use https:// for Subversion checkouts without requiring a password.  In case it matters, we are using Electric Commander for our builds.
>
> I surely can’t be the first one to want to do this.  So what are the best practices surrounding automated builds and secure checkouts via https:// from Subversion servers?  I must be missing something obvious...

Google for "headless gnome keyring", you'll get a ton of solutions.

-- Brane