Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to install Bugzilla under the Linux system to track the bug in program development", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "how to install Bugzilla under the Linux system to track the bug in program development"!

Bugzilla is an open source free Bug (error or defect) tracking system provided by Mozilla, which is used to help you manage software development and establish a complete BUG tracking system.

Bugzilla is a database that collects defects. It allows users to report defects in the software and transfer them to the right developers. Developers can use bugzilla to maintain a priority list of things to do, as well as timelines and tracking dependencies. Not all "bugs" are software defects. Some of the content in the database is as an enhanced request (RFE). A RFE is a Bug with a severity field set to "enhancement". People often say "bug", which actually means a record in Bugzilla, so RFEs is often called bug.

Installation method:

1. Download the Bugzilla source code, and say no more about this.

two。 Install some necessary software packages:

The code is as follows:

Yum install perl-CPAN

Yum install mod_perl

Yum install mod_perl-devel

Yum install fcgi-perl

3. Install the necessary perl modules and check the installation

The code is as follows:

Cd bugzilla

Perl install-module.pl-all

. / checksetup.pl

Of course, it also involves interactive input configurations such as MySQL's username and password.

4. Start the fastcgi wrapper program, download it here (fastcgi-wrapper), and run it.

5. Modify the Nginx configuration file so that it can handle the perl CGI program properly. One of my modifications is as follows:

The code is as follows:

Diff-git a/nginx.conf b/nginx.conf

Index 8730c99..114d9d8 100644

-a/nginx.conf

+ b/nginx.conf

@ @-83 http 10 + 83 charge 20 @ @

# config_apps_end

Location / {

-if (!-f $request_filename) {

-proxy_pass http://jboss8080;

-break

-}

+ root / usr/local/nginx/html

+ index index.html index.htm index.cgi index.pl

+ # if (!-f $request_filename) {

+ # proxy_pass http://jboss8080;

+ # break

+ #}

+}

+

+ location ~\ .pl | cgi$ {

+ root html

+ fastcgi_pass 127.0.0.1 purl 8999

+ fastcgi_index index.pl

+ fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name

+ include fastcgi_params

}

Error_page 500 502 503 504 / 50x.html

6. Finally, change the permissions of the bugzilla directory and restart nginx, such as:

The code is as follows:

Cd / usr/local/nginx/

Chown nobody:nobody html-R

Service nginx restart

Due to the lack of some software packages, the problems and solutions that may arise during installation are as follows:

The code is as follows:

[root@jay-centos html] # perl install-module.pl-all

Can't locate CPAN.pm in @ INC (@ INC contains: / usr/local/nginx/html/lib/x86_64-linux-thread-multi / usr/local/nginx/html/lib/ usr/local/nginx/html/ usr/local/lib64/perl5 / usr/local/share/perl5 / usr/lib64/perl5/vendor_perl / usr/share/perl5/vendor_perl / usr/lib64/perl5/ usr/share/perl5.) At / usr/local/nginx/html/Bugzilla/Install/CPAN.pm line 24.

BEGIN failed-compilation aborted at / usr/local/nginx/html/Bugzilla/Install/CPAN.pm line 24.

Compilation failed in require at install-module.pl line 21.

BEGIN failed-compilation aborted at install-module.pl line 21.

Solution:

The code is as follows:

Yum install perl-CPAN

Can't find mod_perl installed

The error was: Can't locate mod_perl2.pm in @ INC (@ INC contains: / usr/local/nginx/html/lib/x86_64-linux-thread-multi / usr/local/nginx/html/lib/ usr/local/lib64/perl5 / usr/local/share/perl5 / usr/lib64/perl5/vendor_perl / usr/share/perl5/vendor_perl / usr/lib64/perl5/ usr/share/perl5.) At Makefile.PL line 149.

Solution:

The code is as follows:

Yum install mod_perl

Can't locate ModPerl/MM.pm in @ INC (@ INC contains: / usr/local/nginx/html/lib/x86_64-linux-thread-multi / usr/local/nginx/html/lib/ usr/local/lib64/perl5 / usr/local/share/perl5 / usr/lib64/perl5/vendor_perl / usr/share/perl5/vendor_perl / usr/lib64/perl5/ usr/share/perl5.) At Makefile.PL line 60.

Solution:

The code is as follows:

Yum install mod_perl-devel

The code is as follows:

[root@jay-centos html] #. / fastcgi-wrapper

Can't locate FCGI.pm in @ INC (@ INC contains: / usr/local/lib64/perl5 / usr/local/share/perl5 / usr/lib64/perl5/vendor_perl / usr/share/perl5/vendor_perl / usr/lib64/perl5/ usr/share/perl5.) At. / fastcgi-wrapper line 3.

BEGIN failed-compilation aborted at. / fastcgi-wrapper line 3.

Solution:

The code is as follows:

Yum install fcgi-perl

Basic usage of Bugzilla:

1. User login and setup process:

Open the browser and go to the Bugzilla main page.

After entering the main page, click "New account" to enter the registration page.

Enter the E-Mail and real name on the registration page (we all use the computer name here for unification), then click [Create Account], and you will receive an E-Mail containing the initial password.

After receiving the E-Mail, click "Log in", enter the E-Mail address used for registration in the account bar, enter the initial password notified in the email in the password bar, and then click [Login].

If you forget your password, enter the registration user name on the login page, click [Submit Request], and reset the password according to the email you received.

After logging in successfully, click * * Edit Properties * *-> * * account Settings * * to change the password.

Click * * Edit Properties * *-> * * email Settings * * to set email notification.

Click * * Edit attributes * *-> * * permissions * * to query permissions.

2. BUG processing flow

After the tester or developer finds the bug, they determine which module the problem belongs to. After filling in the bug report, the system will automatically notify the project team leader or the developer directly through Email.

According to the specific situation, the project leader will reassign reassigned to the developer to which bug belongs.

After receiving the Email message, ③ developers determine whether it is their own scope of modification.

1) if not, reassign the reassigned to the project leader or the developer who should be assigned.

2) if yes, process it, resolved and give the solution. (patch attachments and supplementary notes can be created)

The ④ tester queries the developer's modified bug for retesting. (test case attachments can be created)

1) after verification, the modified status is VERIFIED. After the whole product is released, it will be changed to CLOSED.

2) there is also a problem, REOPENED, the status changes to "New" again, and an email notification is sent.

⑤, if this BUG hasn't been processed in a week. Bugzilla will continue to harass its owner with email until action is taken. Administrators can set the latest time limit for action, such as 3 days, and the system defaults to 7 days.

3. The submission process of Bug

Click * * New * *-> Select the product name where the found bug is located.

On the bug submission page of the selected product, select or enter bug information.

◎ module: click the word "module" to view detailed information about the module of this product.

◎ platform, operating system: you can choose according to the actual situation of finding bug. If you are sure that this bug can occur on all platforms, choose all!

◎ priority: P1 to P5 priority gradually diminished.

◎ severity: reduced severity from blocker to enhancement.

Blocker: hinders the continuation of project development or testing.

Critical: conflicts, data loss, and serious memory leaks.

Major: a major functional defect.

Minor: minor functional defects.

Trivial: errors in spelling and aligning classes.

Enhancement: it needs to be improved.

Initial state: the developer's default state is "unconfirmed" (this is set by the administrator, see the administrator's instructions). Testers or administrators are optional here: unconfirmed and new.

Assigned to: the default owner for free time is the owner specified by the administrator, or it can be made manually.

CC: can be multiple people, need to be separated by ",".

URL: the location of the bug (optional).

Note: is an overview of bug (required).

The following should be detailed in the Desription:

1) steps to discover the problem

2) what happens after performing the above steps

3) the expected correct results

Keyword: click the "keyword" three words, will display the administrator has set the keyword, select one of them, easy to query. Note: you can't add here at will, you must use existing keywords. In addition, this is the default if the administrator does not create a keyword.

Dependency: directly enter the number of the bug that is dependent on the current bug. To put it simply, for example, if you enter "3" here, it means that the currently submitted bug has a dependency, either because 3 causes the current bug or the current bug causes the bug3.

After confirmation, "commit"!

After submitting, the system will prompt: bug has been submitted. In the lower half of this page, the details of the bug you just submitted will be displayed again. You can modify and re-commit here, or you can add new attachments or additional notes to further explain the bug.

4. Different treatment of Bug

4.1The owner of Bug deals with the problems and puts forward suggestions and solutions.

Give a solution and fill in the additional instructions (Additional Comments). You can also create attachments (e.g. change submission).

Tips for filling in the form:

The problem described by FIXED has been modified, the bug has been fixed and checked, and the source file has been checked into the CVS library.

The problem described by INVALID is not a bug (cancel with this item after an error is entered)

The problems described by WONTFIX will never be fixed.

The problems described by LATER will not be resolved in this version of the product.

The problem described by DUPLICATE is a copy of an existing bug.

All attempts by WORKSFORME to regenerate this bug are invalid. If more information appears, please reassign the bug and just file it now.

4.2 the project leader or developer re-appoints the owner of Bug.

① bug does not fall within its own scope and can be set to Assigned and wait for the tester to reassign it.

② bug is not within its own scope, but knowing who should be responsible, enter the designated person's Email directly in the input box of Reassign bug to.

③ operation result: at this time, the bug status changes to New, and the owner of this bug becomes the specified person.

4. 3 the tester confirms whether the Bug reported by the developer exists.

Query Bug with a status of "Unconfirmed"

The tester confirms the Bug submitted by the developer to confirm the existence of the Bug.

Specific operation: when "Confirm bug (change status to New)" is selected, commit.

Operation result: the status changes to "New".

4.4 the tester verifies the modified Bug

① testers query developers' modified bug, that is, Status is "Resolved" and Resolution is "Fixed". For a retest. (test case attachments can be created)

After the ② has been verified, modify Resolution to VERIFIED. After the whole product is released, it will be changed to CLOSED.

If there is a problem after the test, REOPENED, the status changes to "New" again, and an email notification is sent.

5. Query

After logging in to the Bugzilla defect tracking system, click query, and you can query according to one or more specified query conditions.

Summary (Summary): the drop-down list box selects the query specification. Enter the included information in the input box that follows, and the assignment of this information is consistent with the comment information when the bug was submitted.

Product (Product): select the product where the bugs you are looking for is located.

Module (Component): select the module where the bugs is located.

Version: select the bugs version.

Comments (Comments): you can select the specification that contains information to be entered in the drop-down list box, and then specify the information to be included. This information is specified according to the description information that was filled in when the bugs was submitted.

URL: specify the URL on which the bugs is located.

Keyword (Keywords): specifies the bugs with or without the keyword. Each bug can be assigned a keyword and the bugs reporter or administrator can edit the keyword.

Status (Status): select the bugs status.

Resolution: select the result of bugs processing.

Severity (Severity): select the severity level of bugs.

Priority (Priority): select the priority of the bugs.

Hardware (Platform): select the platform on which bugs programs are running.

At this point, I believe you have a deeper understanding of "how to install Bugzilla under the Linux system to track the bug in program development". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.