Hi Kristis,
other questions for you:
1) We have some problems on a configuration of mail_on_success policy,
because we have more than one commit_mailing_list_email and must to add them
# Must be a valid email address
# To =>
'[EMAIL PROTECTED]',
But if I try to insert two address or more email, SCMBug return an error
when I try to commit an item.
Can we insert more than one mailing list in "To" field? Which is the correct
method?
Besides, we have not a unique mailing list for CVS, but we have more mailing
list referring to each module create within main CVS repository.
For example:
Main Repository
Module Project1 -- Mailing for Project1
Module Project2 -- Mailing for Project2
Module Project3 -- Mailing for Project3
Each time that I commit an item under module project1 a mail will be send
only for all users of the Mailing List for project1 and so on...
We have to create a similar condition. Is it possible? How?
2) In our Glue.conf for valid_product_name policy, we have defined
type=manual, because our SCM is CVS and automatically detected product names
are not supported.
But in our Bugzilla's configuration we have defined many products linked to
CVS Repository. Is possible to insert more than one product name in "Value"
field? How? Or Exist a master value which can group all Bugzilla's products?
valid_product_name => {
enabled => 1,
type => 'manual',
value => 'TestProduct'
},
Thanks in advance
Davide
-----Original Message-----
From: Kristis Makris [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 6:29 PM
To: Davide Giuseppe MAVICA
Cc: [email protected]
Subject: Re: (SCL: 999) [scmbug-users] RE: Integration between Bugzilla and
CVS
On Tue, 2007-01-09 at 17:53 +0100, Davide Giuseppe MAVICA wrote:
> Hi Kristis,
> Thank you for yor help. I have an answer for you.
> I have installed the glue for the bug 120
>
> $ scmbug_install_glue --scm=CVS --product=TestProduct \
> --repository=/tmp/repository --bug=120 --binary-paths=/bin,/usr/bin \
> --daemon=127.0.0.1
>
> If I would to create the integration with another Bug, (For example:
> same product=TestProduct, same repository=/tmp/repository, but
> different bug=130), Do I must to launch another time, the glue
> installer procedure?
No, you don't need to. You only need to run the glue installer just once.
The bug id you supplied (120) is the bug in which the glue installation
itself will be recorded. Actually, it's not recorded at all yet, but I'm
hoping to fix this. After you install the glue, you can begin working on
your projects, commit in CVS and supply any bug id you want when you commit.
Since the glue is installed, it will work with any bug id you supply each
time you commit a change with 'cvs commit'.
> Thanks in advance
> Davide
>
>
>
> -----Original Message-----
> From: Kristis Makris [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 04, 2006 9:41 PM
> To: Davide Giuseppe MAVICA
> Cc: Paolo FALZEA; [email protected]
> Subject: Re: Integration between Bugzilla and CVS
>
> Davide,
>
> I have the feeling that Paolo and you need to read the manual, and in
> particular the section:
>
> http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-15-7/manual/html-
> single
> /manual.html
>
> There's a much more current version available at:
>
> http://www.mkgnu.net/?q=scmbug
>
> including lots of documentation.
>
> On Mon, 2006-12-04 at 16:46 +0100, Davide Giuseppe MAVICA wrote:
> > Hi Kristis,
> > I've installed SCMBUG_RELEASE version 0-15-7 beetwen Bugzilla 2.20.2
> > and
> CVS 1.11.18 on Solaris platform.
> > The Glue.conf file is installed under
> SCMBUG_RELEASE_0-15-7\share\scmbug\glue\etc\scmbug\ path.
> > I must to move the glue.conf files into my CVSROOT path?
> >
> > When I customize the Glue.conf file, I have some difficult to fill
> > some
> parts of it. For example:
> >
> > 1)What do I insert as scm_tool_name??
> >
> > #
> > # Describes the SCM system integrated with bug-tracking
> > #
> > scm => {
> > name => 'replace_with_scm_tool_name',
> >
> > 2)Is it correctly customized bugid_split_regex and log_regex in this
way??
> >
> > # Log template.
> > #
> > # Regular expressions that describe how the bug id and log
> > # comment will be identified must be defined.
> > #
> > # This policy is ALWAYS enabled
> > log_template => {
> > # The bugid_regex is a regular expression that must set
> > # the unnamed variable $1 to the bug number, or list of
> > # bug numbers. It is checked for a match as: m/$regex/s
> > bugid_regex => 'bug\s*(.*?):',
> > # The bugid_split_regex is a regular expression describing
> > # how a list of bug ids will be split in individual bug
> > # numbers. It is split as: /$regex/
> > bugid_split_regex => ',\s?#|\s?#|,|\s+',
> > # The log_regex is a regular expression that must set the
> > # unnamed variable $1 to the log comment. It is checked
> > # for a match as: m/$regex/s
> > log_regex => 'bug.*?:\s*(.*)'
> > },
> >
> > Are there any other parts of Glue.conf file, where I must to focus
> > my
> attention?
> >
> > Thanks in advance
> >
> > Davide
> >
> >
>
>
> _______________________________________________
> scmbug-users mailing list
> [email protected]
> http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
