I used a dumb method:
sudo su hudson
and interactively got and confirmed the certificate for Hudson server.
On Fri, Jun 25, 2010 at 11:41 AM, Kevin Wu <kevinwu.chn_at_gmail.com> wrote:
> I get the following message when executing svn propget:
> Error validating server certificate for 'trunk'(or URL,making no difference):
> - The certificate is not issued by a trusted authority. Use the
> fingerprint to validate the certificate manually!
> - The certificate hostname does not match.
> - The certificate has expired.
> Certificate information:
> - Hostname: Somebody
> - Valid: from Tue, 19 Feb 2008 15:21:30 GMT until Wed, 18 Feb 2009 15:21:30 GMT
> - Issuer: svn, Company, City, Province, Country
> - Fingerprint: fd:17:4a:5a:78:55:a3:f4:ef:1c:cc:49:fd:18:a7:9b:3a:e4:43:32
> (R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'trunk': Server certificate verification failed: certificate has expired, certificate issued for a different hostname, issuer is not trusted (url)
> And it let me enter username and password.
> But in Hudson shell script, such interaction is not desirable. How to
> update the certificate and make it permanent?
> BTW, the subversion server is not maintained by me, so I need to know the
> problem and let the people concerned handle it.
> On Fri, Jun 25, 2010 at 12:59 AM, David Weintraub <qazwart_at_gmail.com>wrote:
>> On Thu, Jun 24, 2010 at 12:53 PM, Kevin Wu <kevinwu.chn_at_gmail.com> wrote:
>> > I was thinking of using the svn:author property.
>> > Is this feasible from the Hudson shell script?
>> > for example,
>> > svn propget svn:author [working copy path] --revprop -r$SVN_REVISIOIN
>> If you're going to use a shell script, it'll look something like this:
>> $user=$(svn propget svn:author http://subversion/repo/path --revprop
>> touch <archive_dir>/Committed_User_-_$user
>> Now, you just set your Hudson job to archive all of the files in
>> <archive_dir>. Then, a user looking at Hudson should be able to see
>> the name of the user who did the commit. BTW, if you use the
>> repository URL instead of the working directory, you won't have to
>> worry about the location of the working directory.
>> David Weintraub
> Best wishes,
> Kevin Wu
Received on 2010-06-25 08:23:31 CEST