Bugzilla when integrated with SVN


Bugzilla is a “Defect Tracking System”, which allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Well,

Subversion (SVN) is a version control system used to maintain current and historical versions of files such as source code, documents, web pages, and libraries.

Although, these two applications are extensively used in standalone mode and rarely in integrated mode — at walking tree we realized that the real beauty is in having SVN integrated with the Bugzilla. It immediately provides us following advantage:

1) We exactly know the code which has been checked-in for a given issue (0r shall I call it which bug ID)

2) As a developer working on code fix, it always helps me to see a consolidated comments — instead of scanning through my past mails

3) The dependency among the code let us know about the dependency among the issues. Thus it provides great input to the deployment team.

Isn’t that really cool? Well, specially for a process oriented organization like Walking Tree, this was a needed integration.

Thank you Ajit for making life easier for the Walking Tree developers. This will help us in having better control on our product development. It will also help us in sharing information transparently with our customers.

Tagged with: , ,
Posted in General
One comment on “Bugzilla when integrated with SVN
  1. wtcindia says:

    It was really interesting to see how the development process easily fits into the Bugzilla + SVN combination. At Walking Tree we follow following process for managing issues
    1) Issues are created with status as NEW
    2) It is assigned to the intended developer
    3) The developer analyze the problem, finds root cause, fixes the issue, add test results and put the issue in UNITTESTED status to indicate that it is pending review.
    4) The reviewer reviews the code changes and test cases and either promote the issue to REVIEWED or demote the issue to ASSIGNED status
    5) The developer promotes the issue to RESOLVED status and makes it available for the build for Integration Testing environment
    6) The developer performing the integration test verifies that issue has been actually fixed and promote the status to ITPASSED
    7) Finally, solution tester ensure that bug is fixed as well as whole system is also in harmony with the new fix
    ——- there you go —– it is ready for customer’s user acceptance test.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

We Have Moved Our Blog!

We have moved our blog to our company site. Check out https://walkingtree.tech/index.php/blog for all latest blogs.

Sencha Select Partner Sencha Training Partner
Xamarin Authorized Partner
Recent Publication
%d bloggers like this: