[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: svn????????

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Thu, 30 Apr 2009 15:51:38 +0200

Well that would be fine, except for security: you'd need to have a generic "build user" (not corresponding to a real person), with fixed password, that has write access to the repository (needs to commit version info, make branches, tags, ...). In our case this means this "user" has to exist in our LDAP in the developers group (only that LDAP group has write access currently).

Our sysadmins don't like such generic user accounts (for one thing: their password tends to be fixed over time to help all the automation, contrary to normal accounts, which are forced to change their password every x months).

That's why we thought: why not let every developer build under his own account (but share the WC to speed up things), and avoid this whole issue.


-----Oorspronkelijk bericht-----
Van: Les Mikesell [mailto:lesmikesell_at_gmail.com]
Verzonden: donderdag 30 april 2009 15:43
Aan: Bob Archer
CC: Johan Corveleyn; users_at_subversion.tigris.org; xuer811
Onderwerp: Re: svn????????

Bob Archer wrote:
>> Hmmm, we were planning to do this in the following scenario:
>> - during normal development, everyone has his own local WC
>> - for building, we use a fixed build machine (*nix machine) with a
>> "shared" WC (we take rotations to perform the build)
>> I guess this sort of WC-sharing should be fine, shouldn't it?
> Yes it "should" be ok. However, why not create a build script and automate it. First, this means only the "automation" is using the WC. And second, your devs don't have to do it manually.

Or start with something like hudson and let it run your automation.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-30 15:52:40 CEST

This is an archived mail posted to the Subversion Users mailing list.