Hello, I'm new to the list, so forgive me if this has been discussed before. I didn't find anything in the archives.
At my workplace, we run a simple home-cooked "gated commit" system on top of Subversion 1.8. Users run their working copy changes through a client program, it assembles all changes and sends them with a work order (what to build, test and run other analysis steps for) to a server, which runs all steps and commits on the user's behalf if they pass. This works really well for us, but we haven't been able to avoid sending the user's SVN credentials together with the work order, and this is clearly not desirable. Is there some way to convince Subversion to commit on a user's behalf? We'd like to designate one SVN account as the commit bot account and let it impersonate users at will. One suggestion that came up internally was to commit as the bot, and then rewrite the revprops with the actual author. We're concerned about race conditions here -- if someone manages to pull changes from the repo between the commit and the revprops change, they'd get an inconsistent view of the world. Since we have many build bots pulling changes and svn sync replicating changes around the world, the risk of this problem is compounded. Ideas welcome, thanks! - Kim
