Hi Laurie, The scmbug glue is both configuration files and Perl code that is installed inside a Subversion repository. It resides under the /hooks directory. It is installed only once, per repository.
When a commit operation is issued by a developer sitting on his desk, the commit operation talks to the Subversion server which kicks off the pre-commit and post-commit scripts on the Subversion server. These invoke the Scmbug glue which opens a connection to the machine hosting the Scmbug daemon and issues operations. The Scmbug daemon then connects to Bugzilla to verify information and write directly to the Bugzilla database. If for example the verification fails, that information is relayed to the Scmbug daemon, and then back to the Subversion server which kicked off the glue, and from there relayed back to the developers client machine. The developer will see such error messages generated from Scmbug right on his screen. On Wed, 2010-11-24 at 16:42 -0500, KRAUS, LAURIE A (ATTCORP) wrote: > Kristis, > > I need to be able to understand the architecture one more level down to > explain to my network administrator how scmbug works (security > concerns). I think I understand the backend piece, but the frontend > piece is still opaque to me. Can you please elaborate on the glue and > how it interfaces to Subversion? Or is it merely configuration info that > the pre-commit and post-commit scripts use? > > Laurie Kraus > > -----Original Message----- > From: Kristis Makris [mailto:[email protected]] > Sent: Tuesday, November 23, 2010 5:55 PM > To: KRAUS, LAURIE A (ATTCORP) > Cc: [email protected] > Subject: Re: [scmbug-users] Need to understand scmbug interfaces better > > Hi Laurie, > > Scmbug uses TCP to communicate from the repository glue to the > integration daemon; the port number is user-configurable. The > architecture diagram in the paper is quite dated. An updated > architecture is found in: > > http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-26-21/manual/html-s > ingle/manual.html#SYSTEM-ARCHITECTURE > > Scmbug currently supports Subversion (up to 1.6.x) and Bugzilla (up to > 3.6.x). > > On Tue, 2010-11-23 at 17:04 -0500, KRAUS, LAURIE A (ATTCORP) wrote: > > I've read through the documentation, including the original paper from > > 2005. But since this info is a few years old, I figured best to ask. > > What protocols/ports/etc. supported by scmbug? I plan to use it to > > integrate Subversion and Bugzilla. Is the architecture shown in Figure > 1 > > still the same or evolved? > > http://files.mkgnu.net/files/scmbug/doc/misc/scmbug_freenix_05.pdf > > > > Thanks, > > > > Laurie A. Kraus > > > > AT&T, Senior Technical Architect > > > > > > _______________________________________________ > > scmbug-users mailing list > > [email protected] > > http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
