[cvsnt] Bug id format?

[Matthew McClellan]

I ran a trace with PostCommandSend enabled and couldn't find any error
message from CVSNT.  Near the very end, there's a line like:

13:52:35: S -> CreateProcess(,C:/CVSMailer/CVSMailer.exe -p00000f80
MMcClellan /CVS_REPOSITORY_20090105 commit)

I'm wondering if that means a separate process was spawned for
CVSMailer, and something CVSMailer then does is what causes the
crashdump?

Any other info I can provide?  The crashdump file?

- Matt

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Matthew McClellan
Sent: Thursday, January 08, 2009 12:46 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Bug id format?

I just noticed that each CVS action - whether it results in an email
sent or not - was generating a crash dump file in the CVS Temp
directory; I would still receive the correct email from CVSMailer
though, and the CVSNT services stay up and running.  I removed all
records in CVSROOT/postcommand and set PostCommandSend=0 in the ini file
and then no crash dump files were created.

Can anyone explain the value of using PostCommandSend?  Is it primarily
to guarantee that all emails are sent, even in the case that a CVS
action takes longer than the ini MailSendDelay value?

Any idea why using PostCommandSend would cause CVSNT to generate a crash
dump?

- Matt

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Matthew McClellan
Sent: Wednesday, January 07, 2009 7:08 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Bug id format?

Sure.  I was able to get links to both JIRA issues and FishEye pages
from CVSMailer.  FishEye is similar to ViewVC.  Both JIRA and FishEye
are Atlassian products.

I think these are the relevent lines from the CVSMailer.ini file:

[IssueTracking]
IssueUrl="JIRA home"/browse/<number>
IssueReference=(bug <number>)
UseIssueLinks=1

[FileLinks]
UseHTMLformat=1
UseDiffLinks =0
UseFileLinks =1

BaseDiffUrl =
DiffCmd=
;This is ViewCvs file markup view:
BaseFileUrl ="FishEye home"/browse/
ModuleCmd =<root>/<module>
FileSummaryCmd=<root>/<module>/<file>
FileCmd =<root>/<module>/<file>

Diffs are a single click from the file link in FishEye.


So in JIRA, let's say there is a project called ABC, and an issue #10;
the URL to that issue is "JIRA home"/browse/ABC-10.  When I commit
changes to CVSNT from TortoiseCVS for that issue, I check the "Mark Bug"
option and enter ABC-10 in the "Bug Number" textbox.

- Matt

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Bo Berglund
Sent: Wednesday, January 07, 2009 6:01 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Bug id format?

On Wed, 7 Jan 2009 00:26:00 -0500, "Matthew McClellan"
<MMcClellan at merkleinc.com> wrote:

>I just recently started using the "Mark Bug" feature, and we happen to 
>be using JIRA for most of our development issue tracking.  In our 
>current environment we have a few separate projects in JIRA whose code 
>is all managed in the same CVSNT repository - running 2.5.04.3226; this

>particular senario needs that prefix to be included in the "Bug Number"
>textbox on commit - otherwise there would be no way of matching that 
>Bug to the correct JIRA project.  Anyway, so far things have worked 
>great; the CVSNT audit database correctly stores the entire string in 
>the BugId column, the commit messages are consistently correct, 
>TortoiseCVS (from
>March-Hare) must be sending the Bug Number correctly too, and even 
>CVSMailer can find the Bug comment and add the correct link to the JIRA

>issue in the email messages.
>
Being the author of CVSMailer I an curious to know how you set CVSMailer
up for handling the JIRA issue links?
What did you put into the ini file for this and how do you enter the
bugid in the commit messages?

I originally constructed the parsing for issue numbers for the Roundup
issue tracker, but tried to make it as general as possible to enable
other systems as well. I have never before heard about JIRA (have not
looked either), but if that is popular I could add some instructions for
that to the CVSMailer website as well...

-- 

/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

Upgrade to CVS Suite for more features and support:
http://march-hare.com/cvsnt/
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

Upgrade to CVS Suite for more features and support:
http://march-hare.com/cvsnt/
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

Upgrade to CVS Suite for more features and support:
http://march-hare.com/cvsnt/