Scmbug
Scmbug integrates software configuration management (SCM) with bug-tracking. It aims to solve the integration problem once and for all. It will glue any source code version control system (such as CVS/CVSNT, Subversion, and Git) with any bug tracking system (such as Bugzilla, Mantis, Request Tracker, Test Director).
| Tags | Software Development Bug Tracking Version Control CVS Subversion Information Management Issue Tracking |
|---|---|
| Licenses | GPL |
| Operating Systems | OS Independent |
| Implementation | Perl |
Recent releases
- 12 May 2009 20:03
Changes: This release adds the ability to map directory names to product names (including the ability to automatically detect product names in CVS 1.12.x), is verified to work against Subversion Subversion 1.5.1 and 1.6.1, and implements WebSVN support for the WebReports for affected files.
- 26 Jan 2009 18:39
Changes: This release fixes the problem of not recognizing the DBI package, improves the performance of log_bugid_regex, log_body_regex, resolution_bugid_regex, resolution_status_regex, and resolution_status_resolution_regex, applies Mantis bugfixes, corrects packaging for RPMs, supports the "UU" property output in Subversion, applies fixes to the Web Reports, and disables the consolidate_cvs_messages, which is defective, by default.
- 17 Oct 2008 21:32
Changes: This release adds partial support for Git integration, begins to report deletions of files in Subversion with the actual revision number instead of "NONE", fixes a bug related to accurately detecting the revision number of a changeset in Subversion when more than one, separate, commit operations are issued at once, adds a WebReport that can email all developers with open bugs during a release, applies bugfixes in the WebReports, applies performance optimizations for activity_get_bugs for TestDirector, and corrects the sorting of bugs in Bugzilla in VDD documents.
- 08 Aug 2008 13:14
Changes: This release applies more design changes in the WebReports, corrects a bug that stopped the daemon from starting, accepts integration from Subversion 1.5.x, and addresses an issue with loading the Bugzilla 3.x packages.
- 06 Jun 2008 20:37
Changes: This release captures STDERR messages in the daemon with log4perl, applies design changes in the WebReports, fixes bugs in the TestDirector backend, and applies the policy valid_product_name on activity_tag operations.
- All comments
Recent commentsBugzilla 3.2.2 and Scmbug 0.26.13
Greetings:
I am working on a proof of concept demo to show that Bugzilla, Testopia, SVN (using Scmbug) can be tied together as one system.
I have the latest version of Bugzilla 3.2.2 installed on Ubuntu Server here. There were some issues with getting Scmbug installed on the same system such as the 'eval { }' issue. But I managed to use various resources to get the Integration Daemon to start properly and the subsequent Glue process to successfully run.
Now I am using Tortoise SVN to attempt to commit changes against project and bug I've specifically created for this. Here is the format:
Bug 15:
Blah blah blah up to 50 characters
Upon doing this I receive the following set of messages:
Commit
temp\NewTestProject\rtf.rtf
temp\NewTestProject\rtf.rtf
Commit failed (details follow):
'pre-commit' hook failed with error output:
Scmbug notice: ---------------------------------------------------------
Scmbug notice: Preparing for VERIFICATION
Scmbug notice: Processing activity
Scmbug notice: Submitting request
Scmbug notice: Request submission was not replied to
Scmbug ERROR> Connection.pm:366:Scmbug::Connection::submit_request -
*******************************************
**
**
** Scmbug error 24: The daemon-spawned connection handler exited abnormally.
Please check the daemon error logs.
The issue seems to be in the Bugzilla.pm code module. I understand these issues may just be par for the course as far as Scmbug compatibility with Bugzilla 3.2.2 is concerned.
Are there workarounds for this incompatibility issue or is it not advisable to try this type of integration?
Thanks
Yus
Re: Installation on windows
I have the same error either.
Does any one has the solution for this.
NB: I used the 0.23.3 version of SCMBUG with 2.22.6 version of Bugzilla and the 1.4.5 version of SVN and Ihave no problem but I want to work with latest stable version 0.26.9 because I am trying to use latest versions of SVN and Bugzilla.
> I'm trying to install on Windows 2003,
> on the same server as my bugzilla
> installation. I'm running ActiveState
> Perl v5.10.0. I have DBI version 1.607
> installed, but I'm getting an error in
> the logs
>
>
> *******************************************
> 2008/12/05 15:53:56 Scmbug WARN>
> Daemon.pm:80:Scmbug::Daemon::Daemon::read_configuration
> - Read configuration file 'C:/Program
> Files/Scmbug/etc/scmbug/daemon.conf'
> 2008/12/05 15:53:56 Scmbug ERROR>
> Daemon.pm:113:Scmbug::Daemon::Daemon::read_configuration
> -
> *******************************************
> **
> **
> ** scmbug error 79: Package 'DBI' v1.50
> not found. v0 found instead.
>
>
> Does anyone know of a way around
> this?
>
Installation on windows
I'm trying to install on Windows 2003, on the same server as my bugzilla installation. I'm running ActiveState Perl v5.10.0. I have DBI version 1.607 installed, but I'm getting an error in the logs
*******************************************
2008/12/05 15:53:56 Scmbug WARN> Daemon.pm:80:Scmbug::Daemon::Daemon::read_configuration - Read configuration file 'C:/Program Files/Scmbug/etc/scmbug/daemon.conf'
2008/12/05 15:53:56 Scmbug ERROR> Daemon.pm:113:Scmbug::Daemon::Daemon::read_configuration -
*******************************************
**
**
** scmbug error 79: Package 'DBI' v1.50 not found. v0 found instead.
Does anyone know of a way around this?
Re: Daemon is not running in 0-26-9 release in windows environment
> I had the same problem; it seems to be
> caused by log4perl. Try
> ppm install Log-Log4perl
> That did the trick for me so that the
> daemon would start.
This is actually documented in section 8.2.3 of the manual - but I didn't see until just now! Doh..
Re: Daemon is not running in 0-26-9 release in windows environment
I had the same problem; it seems to be caused by log4perl. Try
ppm install Log-Log4perl
That did the trick for me so that the daemon would start.