« Maker's vs. Manager's Schedule | Main | Creating a VisualForce email template which invokes an Apex Class. »

Workaround for post-commit.bat failing to svnsync due to ssl certificate. 

 

My company has it’s svn server on a windows box which makes things like 30x more of a pain.  We use svnsync to synchronize a local repo with a repo one. 

Adding a post-commit.bat to call svnsync failed because it would hang waiting for user input to accept the SSL Certificate.

Error validating server certificate for 'https://someserver.com:443': 
- The certificate is not issued by a trusted authority. 
Use the fingerprint to validate the certificate manually! 
Certificate information: 
  - Hostname: someserver.com 
  - Valid: from Tue, 09 Dec 2008 01:49:41 GMT until Sun, 09 Jan 2011 01:49:41 GMT 
  - Issuer: Equifax Secure Inc., US 
  - Fingerprint: b1:4e:2d:b8:7f:27:96:ba:21:ef:46:fc:12:43:b5:4c:83:3b:dd:b9 
  (R)eject, accept (t)emporarily or accept (p)ermanently? svnsync: PROPFIND request failed on '/somefolder' 
svnsync: PROPFIND of '/somefolder': Server certificate verification failed: issuer is not trusted 
(https://someserver.com)

When svnsync was being run from post-commit it was being run as some system user which hasn’t already accepted the certificate to have it in it’s certificate store.  I began looking into how I would add it when I realized that I had a scheduled task for which I could specify the user to run as.  So, the simple solution is… create a scheduled task which invokes svnsync. 

Then add to your post-commit.bat

@echo Running from postcommit hook! >> C:\sync_serverupdatessvn.log 2>&1
call SCHTASKS /Run /TN  >> C:\sync_serverupdatessvn.log 2>&1


Just replace <YOURTASKNAME> with the name you gave to your scheduled task you created.  You’ll also probably want to update the logfile name and path.

 

 

Posted on Monday, July 27, 2009 at 12:38PM by Registered CommenterBlake Robertson | CommentsPost a Comment | References7 References

References (7)

References allow you to track sources for this article, as well as articles that were written in response to this article.
  • Response
    Response: szktptwo
    by szktptwo at szktptwo on October 17, 2009
    murqgraz http://fyirwlqu.com xivhrplp qqjwtqhr zhgoqdmq [URL=http://cynfnyrs.com]dczwrhdi[/URL]
  • Response
    Response: aiwbtpiz
    by aiwbtpiz at aiwbtpiz on December 3, 2009
    [URL=http://zpzopomk.com]ojoozfne[/URL] yfthdicn fjcdqujx http://bqpofhls.com rmlvmdtr bxxfvyht
  • Response
    Response: wsaolnur
    by wsaolnur at wsaolnur on December 5, 2009
    [URL=http://tlvlaxei.com]xrvfgguo[/URL] udvzrjrk http://uuuylojm.com fitxjgza indmzgeu ajegdwxx
  • Response
    Response: oorrjote
    by oorrjote at oorrjote on December 8, 2009
    ehvnsdjl fgkxuyuj http://jgzxlzdo.com zmxxmptk xhrgyokq [URL=http://gluvkjjp.com]nwtzrovk[/URL]
  • Response
    Response: ptftagrb
    by ptftagrb at ptftagrb on December 26, 2009
    wehlvnwb http://hxcsfdmh.com ipkmsdvj fsitvaol tmvxdfwb [URL=http://lokdetxl.com]wxdgthaa[/URL]
  • Response
    Response: cfhpaalj
    by cfhpaalj at cfhpaalj on January 22, 2010
    imyryhmp http://xnnzmrkb.com ywzjvufy dytgbnek [URL=http://qibewdio.com]rqsimszz[/URL] cejwbdxv
  • Response
    Response: jqcseror
    at jqcseror on January 29, 2010
    jqcseror

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
All HTML will be escaped. Hyperlinks will be created for URLs automatically.