Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D01E311278 for ; Wed, 3 Sep 2014 20:08:50 +0000 (UTC) Received: (qmail 8352 invoked by uid 500); 3 Sep 2014 20:08:50 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 8320 invoked by uid 500); 3 Sep 2014 20:08:50 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 8310 invoked by uid 99); 3 Sep 2014 20:08:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2014 20:08:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brane@wandisco.com designates 209.85.215.49 as permitted sender) Received: from [209.85.215.49] (HELO mail-la0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2014 20:08:23 +0000 Received: by mail-la0-f49.google.com with SMTP id b17so10469765lan.22 for ; Wed, 03 Sep 2014 13:08:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wandisco.com; s=gapps; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lW7z3JmWF1TDNfX8GyltT1jovS5xBqhZWOpd134KqMc=; b=qzsN6LyishNmoHA2Az1M2HKhaDxwzeqzatrf1pn1VLQks+pY/AyDFF2MXyRxDmYC1x VbZaH28/azKxXolJ7gvbty6m7UvCEjj7EpFNlgP7SUAmfr2l36HIcTK60O3BeTu6qPqP PQvfYP6druY6roaX/8EyVDlbQf32x3ZHo1b3c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lW7z3JmWF1TDNfX8GyltT1jovS5xBqhZWOpd134KqMc=; b=JyIl4xyk8TIu06kJWszgohL0ZciAjVJjNl1TZCjDh9M+D3lmikVNXPSrhxKoiLM55B 2yUW33Mvp8yaqLZ4GHc4jE43gZtpHrbg+DI8eLa353LPmDjeYn4y1zfkJOS0qFTkPPnU TBQM1JM9QhFMUBlkIp2Qa+jxSbwbKjTP7dHz4KifwslkN+HUUr/hNqZ2bqSe2WerwIXL ecaPAgC2Lsl4NFpM7zQuvx8/HPZzvtS1/HPCjsPee9sBGjTIus5DYCQz7MeXBpGmvl70 b07SF/VD5vCzgVP0aGPLQV2bOHn1LYRdJrkojh/XukeVq+mGtYnTJ5/XDUQ1YIvBvBpB UQvQ== X-Gm-Message-State: ALoCoQl55hKP2XF7ABG3JgGKUOL+NIsQOyQUoybYFnZdaMNClq5po2gtDIlzHwoLTQiSfGrTwyDe X-Received: by 10.112.161.72 with SMTP id xq8mr41210361lbb.18.1409774902383; Wed, 03 Sep 2014 13:08:22 -0700 (PDT) Received: from zulu.local ([77.234.149.122]) by mx.google.com with ESMTPSA id p3sm1482418lap.14.2014.09.03.13.08.20 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 03 Sep 2014 13:08:21 -0700 (PDT) Received: from zulu.local (localhost [IPv6:::1]) by zulu.local (Postfix) with ESMTP id 3B320C6FB585; Wed, 3 Sep 2014 22:08:19 +0200 (CEST) Message-ID: <54077533.9020501@wandisco.com> Date: Wed, 03 Sep 2014 22:08:19 +0200 From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= Organization: WANdisco User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: =?UTF-8?B?S2ltIEdyw6RzbWFu?= CC: users@subversion.apache.org Subject: Re: Commit bot without password References: <54076DFC.206@wandisco.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On 03.09.2014 21:45, Kim Gräsman wrote: > Hi Brane, > > On Wed, Sep 3, 2014 at 9:37 PM, Branko Čibej wrote: >> On 03.09.2014 21:21, Kim Gräsman wrote: >>> 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. >> You could try the following trick: on the build machine, with the bot's >> credentials, do this: >> >> $ svn commit -m ... --with-revprop on-behalf-of=username >> >> then on the server, add a pre-commit hook script that looks at the >> revision properties of the transaction (svnlook propget --revprop) >> that's about to be committed; and if svn:author is the bot, and the >> on-behalf-of property exists, the script would replace the svn:author >> value and delete the on-behalf-of property (svnadmin setrevprop). >> >> This is just a blue-sky idea, I've never actually done that; but I don't >> see a reason, offhand, why it wouldn't work. > Nice idea, sounds promising! > > And as for atomicity, this all happens before the commit transaction > hits the actual repo, right? Yes, that's the whole point of doing this in the pre-commit hook. -- Brane