hook to limit push to only one branch at a time

Question

I’m trying to create a hook that blocks pushes to a remote repository if you are trying to push more than once branch.

Here’s the hook:

#!/bin/bash

HG_EXE="/opt/csw/bin/hg"
CHANGESETS=`${HG_EXE} log -r $1:tip --template '{node} '`

i=0
for changeset in ${CHANGESETS}
do
       BRANCH=`${HG_EXE} log -r ${changeset} --template '{branches}'`

       if [ "${BRANCH}" == "" ]
       then
              BRANCH="default"
       fi
       BRANCHES[$i]=${BRANCH}
       i=$i+1
done

items=${#BRANCHES[*]}
if [ $items -gt 1 ]
then
       i=0
       while [ "${BRANCHES[${i}+1]}" != "" ]
       do
              if [ "${BRANCHES[${i}]}" != "${BRANCHES[${i}+1]}" ]
              then
                     echo "ERROR: You are trying to push more than one branch, use     \"hg push -b [branch_name]\""
                     exit 1
              fi
       i=$i+1 
       done
fi

The problem: If I’ve committed on two branches:

changeset:   58:8d2bebe08dd9
user:        keshurj <Jay.Keshur@monitisegroup.com>
date:        Thu May 26 16:36:49 2011 +0100
summary:     commit on default

changeset:   59:43be74e39a44
branch:      branch1
tag:         tip
user:        keshurj <Jay.Keshur@monitisegroup.com>
date:        Thu May 26 16:40:25 2011 +0100
summary:     commit on branch1

and try to push using hg push –b branch1, the hook still sees ${HG_NODE} as 8d2bebe08dd9, which is on default.

Is there any way to ensure a push is done to only one branch at a time, via a remote hook?

Open to any and all suggestions ( re: this workflow :) )

There's no reason to assume that `8d2bebe08dd9` is the parent of `43be74e39a44` — Matt, May 27 '11 at 18:20

score 2 · Answer 1 · answered May 28 '11 at 03:28

Have you considered just using an alias like hg nudge:

http://hgtip.com/tips/advanced/2009-09-28-nudge-a-gentler-push/

which is just:

[alias]
nudge = push --rev .

That makes sure you only push your current parent revision and its ancestors. which given the assumptions in your script above would probably all be in the same branch (or requires to push that anyway). You need to create a new habit, but it's pretty direct.

score 1 · Answer 2 · answered May 27 '11 at 18:18

1

$1 in your assignment to $CHANGESETS is not defined when the script is run - replace it with $HG_NODE

http://www.selenic.com/mercurial/hgrc.5.html#hooks

This assumes you are running this as a pretxnchangegroup hook. (Tested with hg 1.8.1, but I'm reasonably certain that hasn't changed lately).

answered May 27 '11 at 18:18

Matt

678
1
6
13

Matt, sorry I forgot to mention, I pass in $HG_NODE as an argument for the pretxnchangegroup hook – Jay Keshur May 31 '11 at 08:47

score 0 · Accepted Answer · answered Jun 01 '11 at 11:52

0

turns out i was doing something silly....changeset 58 is the parent of changeset 59.

Thanks guys.

answered Jun 01 '11 at 11:52

Jay Keshur

1
1

hook to limit push to only one branch at a time

3 Answers3