Hi All,
I'm having a difficult time understanding how I should implement a mapping
between products in bugzilla and projects in subversion.
Unfortunately, we cannot have one to one mapping at our site.
Our *products* in bugzilla spawns through multiple subversion *projects*.
Multiple products in buzilla overlaps same source code tree a lot of times.
I understand this is a very common approach and it's not practical to
isolate product --> project mappings at all times.
Let me explain my issue with the following example. Let's say I have these
products and projects in bugzill and SVN respectively:
Bugzilla:
1. Product1
2. Product2
3. Product3
4. Product4
5. Product5
6. Product6
Subversion:
1. /svn/product/java
2. /svn/web
3. /svn/billing
4. /svn/sql
5. /svn/config
I want to understand how do I modify the following section in glue.conf so
that the strict mapping between the product and project is not a constraint
anymore?
product_name_definition => {
values => { '(.*)' => 'Product1' }
},
For the purpose of testing the scmbug implementation, I set it to 'Product1'
and if the checking was made against a bugzilla defect that was for
product1, it would succeed. Else, it would fail.
An alternate suggestion in the SCMBug documentation is to use vendor
branches.
I don't think I'd like to make our development lifecycle complicated with
frequent branching and merging.
It creates a lot of overhead.
Basically, I'd be happy disabling this strictness. Is there a way to do it?
The versions I'm using are:
1. Bugzilla: 3.2.4
2. SCMBug: 0.26.16
Note: I'm referring to the following documentation:
http://files.mkgnu.net/files/scmbug/doc/latest_manual/html-single/manual.html#FIG-PRODUCT-NAME-DEFINITION-AUTO-SCM-STRUCTURE
Thanks,
Girish
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
