Scmbug

We are migrating our CVS + Custom IssueTracker tool chain to SVN + Bugzilla and I came across this tool that allows for some neat integration. I was wondering if the scmbug merger perl script has been completed to allow for real merges as right now it seems to generate just a report of the changesets aka revision number for SVN commits related to the bug.

I have attempted to automate the action of applying a patch in SVN i.e. merge a set of commits on maintenance branch (trunk in this case) that have been tied to bugs in bugzilla to a local working copy of the release branch. The patch is identified by a target milestone in bugzilla. Find below the script. I wish scmbug merger could provide an automated way to do so.

{noformat}
#!/usr/bin/env bash
# read the patch.properties file for patch config
set -- $(cat patch.properties |
awk 'BEGIN { FS="="; } \
/^\#/ { } \
!/^\#/ { if (NF == 2) { print $2; } }')
bugzillaurl=$1
product=$2
repopath=$3
source=$4
sink=$5
milestone=$6
echo bugzilla url: $bugzillaurl
echo source: ${repopath}${source}
echo sink: ${repopath}${sink}
echo project: $product
echo patch: $milestone
# NOTE: local working copy must be the checkout of the sink i.e. release branch that you want to merge into
# backup the patch.properties before you revert you local changes on your working copy
cp 'patch.properties' ~/'test.prop'
#rm 'patch.properties'
svn revert --depth=infinity .
mv ~/'test.prop' 'patch.properties'
# Query bugzilla by product and target milestone (patch label) and get the list of bugs part of the target milestone (aka patch)
curl -s "$bugzillaurl/buglist.cgi?product=$product&target_milestone=$milestone" 2>&1 | awk -F '[<>]' '/show_bug/ && $3 !~ /[^0-9]/ {if($3 != "") array[n++] = $3}
END { result = array[0];for( i=1; i | sort -un | xargs -L 1 -I % svn merge -c % ${repopath}${product}${source}
done
{noformat}

We are migrating our CVS + Custom IssueTracker tool chain to SVN + Bugzilla and I came across this tool that allows for some neat integration. I was wondering if the scmbug merger perl script has been completed to allow for real merges as right now it seems to generate just a report of the changesets aka revision number for SVN commits related to the bug.

I'd rather not. We prefer issues to be reported to the project's mailing list, where they are visible by all, not just me.

@mkgnu: You can click the feed icon next to "All comments" above to subscribe to this page's comments ( freshmeat.net/projects... ).

Sincerely,
Jeff

Please don't add support comments here, because we simply don't know when one is added.

Instead ask for help on the project's mailing list.