Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Strictly speaking, Bugzilla and SVN don't necessarily have anything to do with each other. They are completely separate programs.
As Agrouf said, Bugzilla allows you to create and manage "bugs". It keeps a history from when a problem or issue was first reported, through when and how it was resolved.
Subversion, on the other hand, is a "version control system". It keeps a record of all code changes. SVN doesn't link back to Bugzilla, and Bugzilla doesn't link to SVN. The same is equally true of any version control system: SVN, CVS, VSS, etc etc.
So how the two systems (version control and bug tracking) related?
Typically "by convention".
When you change source code to make a bug fix, your developers will generally write the bug# as a comment in the source checkin. By the same token, when a bug is closed, the developer will typically write the source version# as a comment in the bug report.
Thanks Paul..
My PM has asked me to install Bugzilla for SVN. I read the link sent bu Agrouf for Integrating SVN and Bugzilla and had Bugzilla working on my Linux Machine. But I am not able to find the point to point steps for the same. Which file to edit?
Google said there is a script at http://sean-janus.optionpc.com/me/software/bugtraq/ but that too unreachable.
Can You help me with hint what exactly I shud do?
There *are* no "point to point steps" for integrating Bugzilla and Subversion. Any more than integrating Visual Source Safe (for version control) and MS Sharepoint (for bug tracking).
It's entirely possible you're done actually *done*, if:
a) Bugzilla is installed and working
b) You've defined the components and sub-components that Bugzilla will track
c) You've set it up so that users can log on to Bugzilla
Talk to your project manager and see what (if anything) he (or she) would like you to do from here.
Well, most of the time, SVN and bugzilla are used next to each other and there is no automatic integration at all. Developers just put their bugId in svn commits and their revision id in bugzilla. They do it manually.
What you can do to make svn work with bugzilla for instance is to use the post-commit script to send an email to bugzilla and use bugzilla's email_in.pl script to append a comment to the bug saying for instance that svn revision ### fixes that bug.
This is explained in the link provided, in the "SVN Configuration" section.
most of the time, SVN and bugzilla are used next to each other and there is no automatic integration at all. Developers just put their bugId in svn commits and their revision id in bugzilla. They do it manually.
In other words:
Quote:
When you change source code to make a bug fix, your developers will generally write the bug# as a comment in the source checkin. By the same token, when a bug is closed, the developer will typically write the source version# as a comment in the bug report.
Sooooooo.....
You've gone just about as far as you can with "out of the box" functionality. In essence, you're probably "done". Congratulations!
You really need to talk to your Project Mgr to see what - if anything - he wants to do from here.
Sorry I repeated what paulsm4 said. I didn't realize there was a 2nd page to this thread when I replied. I thought the last post was the last one of page 1.
Agrouf - no apologies necessary. I'm just glad we're in agreement with each other :-)
The point I wanted to emphasize is that your_shadow03 has gone has far as he realistically can with what we *know* needs to be accomplished. Thanks in no small part thanks to your help, Agrouf. Good job!
There are other things that *could* be done (your link to using MediaWiki to provide a common UI to both SVN and Bugzilla is a good example. One of many, many possibilities).
But, since the OP is doing this for his team, on behalf of his project manager ... I believe it would be unwise to proceed any further without touching bases with the project manager.
Thanks to you both for advising me with this thread.
But Still something remain doubtful for me.
Hope I could understand. What I recall :
Last Year I installed TRAC and configured SVN to work with TRAC and that worked.I mentioned that too in one of my Blogs(http://www.linuxquestions.org/blog/y...on-linux-1146/).
Developers login and could Browse the overall projects and source codes.
Trac I understand is Bug Tracking Tool and so do Bugzilla.Now how come Bugzilla different from Trac functionality?
Correct me if I am really mistaken with the term.How Can I see SVN projects and user login into SVN through same WebDAV Pasword. I can login into TRAC with same password for all users which I setup with SVN WEBDAV.
I am really sorry if i am not able to understand.May be one more attempt can make me think a bit more.
Sorry..If this thread and my understanding is really panic for you both.
Well, I believe you need to define "working with". What do you expect svn to do with bugzilla when you say "configure svn to work with bugzilla" exactly?
Take an example of TRAC. Becoz I am familiar with that.It is Bug tracking tool and works with SVN with few tweaking. Isn't it? Bugzilla is too Bug Tracking Tool.Cant we have SVN included on the same.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.