Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#5 svn:author not the same as svn:log

open
Erik H
None
3
2012-09-01
2012-08-29
Eric
No

So I'm confused as to why the svn:author in the revision properties is not always the same as the PeopleSoft user you are adding in the message of the svn:log. I have added all the svnusers in the DecodePC.properties file and also modified the passwd file in the repository. Any suggestions?

Discussion

  • Erik H
    Erik H
    2012-09-01

    Known problem - the mapping from PS to SVN users does not work well.

    The PS user that is listed in the log message is correct.

    I suspect there is some caching going on in the SVNKit library, the code that does the actual mapping seems to work.

    On my to-do list but with a low priority (perhaps I'll give up and get rid of the mapping).

     
  • Erik H
    Erik H
    2012-09-01

    • priority: 5 --> 3
    • assigned_to: nobody --> erikh3
     
  • Eric
    Eric
    2012-09-04

    I haven't worked with this enough to really tell you if there is a huge benefit to having the svn author = PS OPRID. Only thing I could think of is if you wanted a list of customized/delivered customized objects, but you can get that directly from the database. It may suffice just to have a default svn author for every commit. Not sure if there is a way to add a property to a commit where you could separate out the LASTUPDOPRID and LASTUPDDTTM fields.