Hi Deng, no thats not the problem, my Hudson User for Archiva is Global Repository Manager, so he has all rights granted...
Greetings, Simon. -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Maria Odea Ching Gesendet: Mittwoch, 27. August 2008 12:30 An: [email protected] Betreff: Re: Users get locked Could you possibly be using the same credentials for your proxy repo & your deployment repo but you don't have the repo manager role for the deployment repo and trying to deploy to it (during the nightly build) caused the account to be locked? (This happened to me before :) Thanks, Deng On Wed, Aug 27, 2008 at 3:53 PM, von Janowsky, Simon <[EMAIL PROTECTED] > wrote: > Hi, > I still have this problem with user(s) that get locked automatically. > Yesterday our build System (Hudson) worked fine all day, but when I > came into the office this morning, Archiva had locked the User for the > build system again. > I have a feeling that this will alway happen ovenight, as if are > there cron jobs in Archiva that check the users? And lock them? > Can I workaround this? Like setting a flag in the database? > > Since my last post I pdated the derby to newest version, should I > perhaps use mysql instead? > > Greetings, > Simon. >
smime.p7s
Description: S/MIME cryptographic signature
